Harden GitHub Actions dependencies and permissions - #638
Merged
Conversation
This was referenced Aug 21, 2026
This was referenced Aug 21, 2026
Contributor
Author
|
/snapit |
marvinhagemeister
approved these changes
Aug 24, 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
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 changed
This updates the GitHub Actions used by the repository and pins each external action to a reviewed commit. It also adds a seven-day delay before Dependabot proposes newly released action versions.
Future GitHub Action updates will be grouped into one pull request. Dependabot will keep Changesets on v1 until the repository deliberately upgrades to Changesets CLI v3.
The workflows now declare the permissions they need instead of inheriting the repository's broad defaults. Checkout credentials are no longer left available to later steps.
The custom GitHub App token is now used only by Changesets, where it is needed so updates to the release PR trigger the usual checks. Preview publishing and Snapit use the job's built-in GitHub token.
The workflows continue to use
ubuntu-latest, and the maintenance policy is documented inCONTRIBUTING.md.Validation
The protected release, preview, CLA, and Snapit event paths will be checked through their normal repository events after merge rather than simulated locally with production credentials.
No changeset is needed because this changes repository automation and documentation only.