ci: default workflow tokens to read-only contents - #1218
Merged
Conversation
github-actions
Bot
added
T-CI
jamadeo
marked this pull request as draft
August 25, 2026 18:43
7 tasks
jamadeo
force-pushed
the
jamadeo/restrict-workflow-token-defaults
branch
from
August 25, 2026 18:49
5a1cacb to
f8fff78
Compare
jamadeo
changed the title
jamadeo
marked this pull request as ready for review
August 25, 2026 18:50
DaleSeo
approved these changes
Aug 27, 2026
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
2 participants
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.
Summary
Sets an explicit read-only
contentspermission default on workflows that previously relied on GitHub's repository-level token defaults. This allows checkout—including in the crates.io release job—while preventing implicit write access. Existing job-level grants remain unchanged for jobs that require additional permissions.Addresses the default token-permission findings tracked in #1215. Release-plz and the coverage job's explicit write permissions are reviewed separately.