ci: restore publish job with id-token permission - #122
Merged
Conversation
Startup bisecting showed 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. The release cascade caller (release-on-merge.yml publish-production) already grants id-token: write, so the real cascade path is valid; this commit simply restores the publish job and pypa action after the diagnostic round-trip.
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.
Rebuilds the publish job of python-publish.yml (id-token: write + pypa publish action) after the startup-failure bisect. The release cascade caller already grants id-token: write, which is required for the nested job declaration to parse. Diagnostic workflows removed.