Repository navigation
chore: pin GitHub Actions to SHAs and drop persisted tokens - #16
Merged
Merged
Conversation
Contributor
API Changes Report
Summary
No API Changes DetectedAll packages have stable APIs with no detected changes. Report generated by snapi |
commit: |
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.
Every third-party action under
.github/workflows/**andaction.ymlis now pinned to an immutable commit SHA, with the original tag kept as a# v4comment. 13uses:references across 4 workflows and the composite action.persist-credentials: falseis set on everyactions/checkoutthat doesn't need the persisted token. The one site that does,release.yml, is intentionally left alone:changesets/actionneeds the persistedGITHUB_TOKENto push the Version PR back to the repo. An inline comment above that checkout documents why..github/dependabot.ymlis new; it groups github-actions updates into a single weekly PR so the SHAs stay current without manual babysitting. This is the lightweight equivalent of the Renovate piece in clerk/javascript#8632, which this repo doesn't run.