ci: add explicit permissions to release workflows - #7945
Open
theamitmehra wants to merge 1 commit into
Open
Conversation
Adds top-level permissions blocks to prep-release.yml, publish-changelog.yml, and publish-release.yml, which were missing explicit permissions and defaulting to read-write. Part of improving OpenSSF Scorecard Token-Permissions score. Relates to jupyter#7941
Contributor
|
|
Author
|
Hi! Could a maintainer please add the appropriate triage label to this PR? I don't have permission to add labels as a first-time contributor. Thanks! |
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.
What
Adds explicit top-level
permissions: contents: readto three releaseworkflows that were missing permissions blocks entirely:
Job-level write permissions are preserved where needed (contents: write
in prep-release, id-token: write in publish-release).
Why
Without explicit permissions, GitHub Actions defaults the GITHUB_TOKEN
to read-write, which is broader than needed. This is flagged as
Token-Permissions (0/10) in the OpenSSF Scorecard.
Relates to #7941