chore(release): add OIDC availability diagnostic#238
Merged
Conversation
Prints whether ACTIONS_ID_TOKEN_REQUEST_URL is present to determine if GitHub is actually granting id-token: write. Presence only, never the value.
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
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.
Temporary diagnostic to disambiguate the
ENEEDAUTHpublish failure.Adds a step that prints whether
ACTIONS_ID_TOKEN_REQUEST_URLis present (presence only — never the value). GitHub only injects that env var whenid-token: writeis actually granted.After merging, re-run the Release workflow and read the Debug OIDC availability step:
Revert this once the release is green.