Skip to content

ci: Use client-id for the GitHub App token - #88

Merged
samuelburnham merged 1 commit into
mainfrom
ci/app-token-client-id
Aug 24, 2026
Merged

ci: Use client-id for the GitHub App token#88
samuelburnham merged 1 commit into
mainfrom
ci/app-token-client-id

Conversation

@samuelburnham

Copy link
Copy Markdown
Member

actions/create-github-app-token@v3 renamed app-id to client-id and attached a deprecation message to the old name, which every run that mints a token now prints as a warning. The input is passed straight through to @octokit/auth-app as appId, which accepts an App ID or a client ID, so the existing TOKEN_APP_ID secret works unchanged and callers need no update.

actionlint's bundled metadata for the action predates the rename, so it reports client-id as unknown and app-id as missing. Filter those two messages in actionlint.yaml until it refreshes; the patterns name the action, so a genuine typo in either input is still caught.

`actions/create-github-app-token@v3` renamed `app-id` to `client-id` and
attached a deprecation message to the old name, which every run that mints
a token now prints as a warning. The input is passed straight through to
`@octokit/auth-app` as `appId`, which accepts an App ID or a client ID, so
the existing `TOKEN_APP_ID` secret works unchanged and callers need no
update.

actionlint's bundled metadata for the action predates the rename, so it
reports `client-id` as unknown and `app-id` as missing. Filter those two
messages in `actionlint.yaml` until it refreshes; the patterns name the
action, so a genuine typo in either input is still caught.
@samuelburnham
samuelburnham merged commit 19760cb into main Aug 24, 2026
1 check passed
@samuelburnham
samuelburnham deleted the ci/app-token-client-id branch August 24, 2026 19:19
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