chore(ci): pin some lingering actions by hash - #15016
Merged
Merged
Conversation
I did this automatically with `pinact run -v` and then cross-checked with `zizmor`'s impostor commit audit. Signed-off-by: William Woodruff <william@astral.sh>
woodruffw
temporarily deployed
to
uv-test-registries
August 1, 2025 18:50 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
woodruffw
temporarily deployed
to
uv-test-publish
August 1, 2025 18:50 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
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.
This is the first of several burndown PRs for CI.
I did this automatically with
pinact run -vand then cross-checked with
zizmor'simpostor commit audit.
Summary
This takes our remaining ref-pinned GitHub Actions usage and hash-pins them. In other words,
@v1becomes@feedfacefeedface....Doing this makes our action usage de facto immutable, at least at the repository state level -- the actions themselves might still be non-idempotent/hermetic/reproducible, but the repository state itself can't change like it could before with a tag overwrite.
Test Plan
This should be a non-functional change. However, the only way to really confirm that is to run the CI and see what happens 🙂