Skip to content

ci: use client-id for create-github-app-token#52

Merged
ouun merged 1 commit into
mainfrom
chore/gh-app-token-client-id
Jun 9, 2026
Merged

ci: use client-id for create-github-app-token#52
ouun merged 1 commit into
mainfrom
chore/gh-app-token-client-id

Conversation

@ouun

@ouun ouun commented Jun 9, 2026

Copy link
Copy Markdown
Collaborator

Fixes the deprecation warning from the asset-build job:

Input 'app-id' has been deprecated with message: Use 'client-id' instead.

actions/create-github-app-token@v3 deprecated app-id in favor of client-id. This switches the input.

⚠️ Prerequisite before merging

The Client ID is a different value from the numeric App ID, so the existing MILLIPRESS_BOT_APP_ID secret can't be reused. Add a MILLIPRESS_BOT_CLIENT_ID secret (org-level, matching the other MILLIPRESS_BOT_* secrets) holding the bot app's Client ID — found at Settings → Developer settings → GitHub Apps → [the bot app] → Client ID (format Iv23li…).

If this merges before that secret exists, the push-time "Build & Commit Assets" step will fail (empty client-id). The Client ID isn't sensitive, so an Actions variable (vars.MILLIPRESS_BOT_CLIENT_ID) would also work if you'd prefer that over a secret — say the word and I'll switch it.

Verified against the action README (v3.2.0): client-id is recommended; app-id still works but is deprecated.

create-github-app-token@v3 deprecated the app-id input in favor of
client-id. Switch to client-id, backed by a new MILLIPRESS_BOT_CLIENT_ID
secret (the bot app's Client ID, distinct from its numeric App ID).
@ouun ouun merged commit ce2a064 into main Jun 9, 2026
5 checks passed
@ouun ouun deleted the chore/gh-app-token-client-id branch June 9, 2026 09:00
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