chore(ci): bump socket-registry refs to b9918c72#1277
Merged
John-David Dalton (jdalton) merged 1 commit intomainfrom Apr 25, 2026
Merged
chore(ci): bump socket-registry refs to b9918c72#1277John-David Dalton (jdalton) merged 1 commit intomainfrom
John-David Dalton (jdalton) merged 1 commit intomainfrom
Conversation
… fleet alignment) Propagation SHA bump. socket-registry's current main tip carries the .pnpmrc → pnpm-workspace.yaml rework (pnpm v11 doesn't read .pnpmrc; settings that matter live in pnpm-workspace.yaml or .npmrc). socket-registry Layer 4 workflows (_local-not-for-reuse-*) are pinned to b9918c72; downstream repos pin to the same SHA so the fleet references the same socket-registry tip. No workflow behavior change — the .github/actions/* contents are identical between f1b40c99 and b9918c72 (the intervening commits only touched .pnpmrc and pnpm-workspace.yaml).
Dale Bustad (divmain)
approved these changes
Apr 25, 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.
Propagation SHA bump. socket-registry's current main tip carries the .pnpmrc → pnpm-workspace.yaml rework (pnpm v11 doesn't read .pnpmrc; settings that matter live in pnpm-workspace.yaml or .npmrc).
socket-registry Layer 4 workflows (
_local-not-for-reuse-*) are pinned tob9918c72; this PR pins the same SHA here so the fleet references the same socket-registry tip.No workflow behavior change — the
.github/actions/*contents are identical betweenf1b40c99andb9918c72(the intervening commits only touched.pnpmrcandpnpm-workspace.yaml).Note
Low Risk
Low risk because this only updates pinned
SocketDev/socket-registrycomposite-action SHAs in GitHub workflows, with no product code or logic changes. The main risk is CI/publish behavior drifting if the referenced action revision differs unexpectedly.Overview
Updates CI/publish automation to pin all
SocketDev/socket-registryreusable actions tob9918c72…instead off1b40c99…acrossci.yml,provenance.yml, andweekly-update.yml.This keeps workflow dependencies aligned to the same socket-registry tip (including
setup-and-install,setup-git-signing, andcleanup-git-signing) without changing the workflows’ own steps or commands.Reviewed by Cursor Bugbot for commit 61c2caa. Configure here.