chore(ci): bump socket-registry action SHAs#161
Merged
Conversation
jdalton
force-pushed
the
chore/bump-socket-registry-sha
branch
2 times, most recently
from
6dd3d9c to
d3be60b
Compare
jdalton
force-pushed
the
chore/bump-socket-registry-sha
branch
from
d3be60b to
279c3ab
Compare
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.
Summary
Bump socket-registry action SHAs to the latest main after the full Layer 1-4 cascade (#209, #210, #211, #212).
What changed upstream
pnpm/action-setupreplaced with direct binary download (v10.33.0, checksum-verified)zizmor-actionreplaced with native binary (v1.23.1, checksum-verified)