ci: grant id-token to verify-dry-run caller - #123
Merged
Conversation
A reusable-workflow job that declares id-token: write makes GitHub reject the whole call chain at parse time unless every intermediate caller grants the same permission - even if the job would be skipped. Grant it to verify-dry-run (publish=false never triggers the publish job, so the permission is unused in practice).
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.
GitHub rejects a reusable-workflow chain at parse time when a nested job declares id-token: write but an intermediate caller does not grant it - even if that job would be skipped. Grant the permission to verify-dry-run so both callers of python-publish.yml satisfy the requirement.