ci: add top-level permissions: read-all to workflows#57
Merged
Conversation
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.
Resolves TokenPermissionsID Scorecard alerts #57 and #58.
Adds
permissions: read-allat the top level of bothfunctional-tests.ymlanddocker-publish.yml. This sets a secure read-only default for the GITHUB_TOKEN. Each job indocker-publish.ymlalready has its own minimal job-level permissions — those are unchanged.Alert #79 (
contents: writeon themergejob) will remain as an informational warning since git tag creation legitimately requires it.No version bump — CI-only change.
🤖 Generated with Claude Code