Skip to content

fix(ci): read the org app credentials in the update check - #43

Merged
azlekov merged 1 commit into
mainfrom
fix/update-check-app-token
Nov 9, 2026
Merged

azlekov merged 1 commit into
mainfrom
fix/update-check-app-token

Conversation

@azlekov

@azlekov azlekov commented Nov 9, 2026

Copy link
Copy Markdown

The scheduled "Check for SDK, JDK, and Node updates" workflow has failed on every run since at least 2026-10-26. It stops at "Create GitHub App token" with The 'client-id' (or deprecated 'app-id') input must be set to a non-empty string.

The workflow reads secrets.APP_ID and secrets.APP_PRIVATE_KEY, but the repo defines no secrets of its own. The org provides the app credentials as GH_APP_CLIENT_ID and GH_APP_PRIVATE_KEY, shared with all repos. This change switches to those and uses the client-id input, which also clears the app-id deprecation warning.

Verify after merge by dispatching the workflow manually.

🤖 Generated with Claude Code

The scheduled SDK/JDK/Node update check read APP_ID and APP_PRIVATE_KEY, which
this repository does not define, so the token step failed on every run. Use the
org-level GH_APP_CLIENT_ID and GH_APP_PRIVATE_KEY through the client-id input.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@azlekov
azlekov merged commit 28c6edb into main Nov 9, 2026
11 checks passed
@azlekov
azlekov deleted the fix/update-check-app-token branch November 9, 2026 12:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant