Skip to content

fix: migrate app-id to client-id in workflow app tokens#92

Merged
patchloom-release[bot] merged 1 commit into
mainfrom
fix/app-token-client-id
Jun 6, 2026
Merged

fix: migrate app-id to client-id in workflow app tokens#92
patchloom-release[bot] merged 1 commit into
mainfrom
fix/app-token-client-id

Conversation

@SebTardif
Copy link
Copy Markdown
Contributor

The app-id input for actions/create-github-app-token@v3 is deprecated and will stop working when GitHub forces Node.js 24 (June 16, 2026). Both auto-approve.yml and release.yml are updated to use client-id with a repository variable (vars.APP_CLIENT_ID) instead of the numeric App ID secret.

The Client ID is not sensitive (it is public on the App settings page), so it is stored as a variable rather than a secret.

Also added APP_CLIENT_ID as a repository variable via gh variable set.

The `app-id` input for `actions/create-github-app-token@v3` is
deprecated and will stop working when GitHub forces Node.js 24
(June 16, 2026). Migrate both workflows to use `client-id` with a
repository variable (`vars.APP_CLIENT_ID`) instead of the numeric
App ID secret.

The Client ID is not sensitive (it is public on the App's settings
page), so it is stored as a variable rather than a secret.

Signed-off-by: Sebastien Tardif <sebtardif@ncf.ca>
@patchloom-release patchloom-release Bot enabled auto-merge (squash) June 6, 2026 15:51
@patchloom-release patchloom-release Bot merged commit 68b9fc8 into main Jun 6, 2026
19 checks passed
@patchloom-release patchloom-release Bot deleted the fix/app-token-client-id branch June 6, 2026 15:54
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