Repository navigation
fix(ci): match the immutable GitHub OIDC subject - #13
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
The first Cloud Run deployment was rejected by the federation condition because this repository uses GitHub's immutable OIDC subject format. The setup script expected the older name-only format.
Use the exact subject reported by the repository's OIDC customization API: repo:souravC01@114119117/JobHelperGuru@1355476075:ref:refs/heads/main. Apply it consistently to the provider condition and deployer impersonation binding, and document how to verify the format before recreating federation. All existing repository, owner, branch, event, and workflow restrictions remain.
Validation: the script's subject matches the live GitHub configuration; Bash syntax passes; all 13 deployment-path scenarios and permission/gate assertions pass; zero-dash scan and git diff --check pass. The live provider and binding were corrected to this exact subject, and the obsolete subject binding was removed. Production workflow 34682469772 passed on retry: keyless authentication, image push, Cloud Run image update, and Vercel health verification all succeeded. Both branch and PR CI runs and the Vercel preview check also passed.
Only setup documentation and the one-time bootstrap script change. No application code, workflow behavior, or Render configuration changes.