fix(ci): use client-id for create-github-app-token v3#148
Merged
Conversation
The v3 action renamed `app-id` to `client-id` and requires the GitHub App's Client ID instead of the numeric App ID. Update both workflows to use the new `SCOPE3_WIZARD_CLIENT_ID` org variable.
nastassiafulconis
approved these changes
Apr 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The recent Dependabot bump of
actions/create-github-app-tokenfrom v2 to v3 (#139) broke the release and regenerate-schemas workflows. v3 renamed theapp-idinput toclient-idand requires the GitHub App's Client ID instead of the numeric App ID.release.ymlandregenerate-schemas.ymlto useclient-idwith the newSCOPE3_WIZARD_CLIENT_IDorg variable.Test plan
mainand confirm the release workflow triggers successfully