Skip to content

chore(ci): bump socket-registry refs to 0371e83f#188

Merged
John-David Dalton (jdalton) merged 2 commits intomainfrom
chore/registry-sha-bump-0371e83f
Apr 24, 2026
Merged

chore(ci): bump socket-registry refs to 0371e83f#188
John-David Dalton (jdalton) merged 2 commits intomainfrom
chore/registry-sha-bump-0371e83f

Conversation

@jdalton
Copy link
Copy Markdown
Collaborator

Bumps SocketDev/socket-registry workflow/action pins to 0371e83f.

This is the Layer 3 propagation SHA from socket-registry's recent cascade adding a runtime guard to the install action: it now fails fast with an actionable message when the consumer's @socketsecurity/lib is below the latest version published to npm. Below-floor versions ship a stubbed pacote fetcher that throws inside downloadPackage when the install action provisions ecc-agentshield.

socket-lib already pins @socketsecurity/lib-stable at 5.24.0 (the current npm latest), so this is a mechanical bump — no consumer code changes.

Test plan

  • CI pipeline (check + matrix tests) passes
  • Audit GitHub Actions check passes

Picks up the @socketsecurity/lib floor enforcement that landed in
socket-registry 24ad6b61 — the install action now fails fast with
an actionable message when the consumer's @socketsecurity/lib is
below the latest version published to npm.

socket-lib already pins @socketsecurity/lib-stable at 5.24.0 (the
floor), so this bump is mechanical — no consumer code changes.
The previous propagation SHA (0371e83f) shipped a guard step whose
version_lt function exploded when npm view returned a Socket Firewall
banner string instead of a version. f1b40c99 validates npm view
output as semver before using it.
@jdalton John-David Dalton (jdalton) merged commit ee14dd4 into main Apr 24, 2026
10 of 11 checks passed
@jdalton John-David Dalton (jdalton) deleted the chore/registry-sha-bump-0371e83f branch April 24, 2026 20:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants