chore(ci): bump create-github-app-token from v1 to v3#152
Open
flitzrrr wants to merge 1 commit into
Open
Conversation
v1 is two major versions behind. v3.2.0 (released 2026-05-12) adds handling for the X-GitHub-Stateless-S2S-Token header that GitHub introduced for the upcoming installation-token format rollout: https://github.blog/changelog/2026-05-15-github-app-installation-tokens-per-request-override-header/ Floating @V3 picks up the v3.x line so future patch/minor releases arrive automatically.
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
1 participant
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
actions/create-github-app-tokenfrom@v1to the floating major@v3in.github/workflows/warden.yml.@v1is two major versions behind upstream. v3.2.0 (released 2026-05-12) adds explicit handling for the newX-GitHub-Stateless-S2S-Tokenheader that GitHub introduced as part of the upcoming installation-token format rollout — see the GitHub Changelog from 2026-05-15.@v3keeps Warden on the supported major and picks up future patch/minor releases without further bumps.Why
GitHub is rolling out a new stateless (JWT) installation-token format. Recent versions of
actions/create-github-app-tokenhandle the rollout transparently. Older@v1is still maintained at best on a best-effort basis and missed several refactors of the underlying token-issuance flow.Test plan
Wardenworkflow runs successfully on this PR.actions/create-github-app-token@v3resolves to v3.2.0 (or newer) and produces a valid token for thegetsentry/warden@v0step.