Skip to content

chore(ci): bump socket-registry actions to 444b6415 (scan auto-skip)#611

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

chore(ci): bump socket-registry actions to 444b6415 (scan auto-skip)#611
John-David Dalton (jdalton) merged 2 commits intomainfrom
chore/registry-sha-bump-13684cd8

Conversation

@jdalton
Copy link
Copy Markdown
Contributor

@jdalton John-David Dalton (jdalton) commented Apr 22, 2026

Bumps SocketDev/socket-registry action/workflow pins to 444b6415.

Rolls up all three successive cascades into a single pin bump:

  1. tool-envs (7ca50837): setup/action.yml exports SOCKET_TOOL_PNPM_*, SOCKET_TOOL_SFW_*, SOCKET_TOOL_ZIZMOR_*, SOCKET_TOOL_AGENTSHIELD_*, SOCKET_TOOL_NODE_VERSION. @socketsecurity/lib resolvability guard + AgentShield install via downloadPackage.
  2. checksums-file (fd589015): setup/action.yml adds SOCKET_TOOL_CHECKSUMS_FILE env var pointing at a stable on-runner copy of external-tools.json, usable as a Docker build-context COPY source so Dockerfiles can verify pnpm/zizmor/etc. tool checksums without duplicating per-platform SHAs.
  3. matrix scan auto-skip (444b6415): zizmor + ecc-agentshield installs now auto-skip in matrix test cells via strategy.job-total < 2. No user-facing input — PR authors cannot disable scans via workflow inputs. Scans still run exactly once in single-cell jobs (check / lint / type-check).

Mechanical bump; no consumer code changes in this repo.

@jdalton John-David Dalton (jdalton) force-pushed the chore/registry-sha-bump-13684cd8 branch from 4e96eba to ea8d87f Compare April 24, 2026 15:58
@jdalton John-David Dalton (jdalton) changed the title chore(ci): bump socket-registry actions to 13684cd8 (gh telemetry opt-out) chore(ci): bump socket-registry actions to 7ca50837 (tool-envs cascade) Apr 24, 2026
@jdalton John-David Dalton (jdalton) force-pushed the chore/registry-sha-bump-13684cd8 branch from ea8d87f to 7487ab8 Compare April 24, 2026 16:31
@jdalton John-David Dalton (jdalton) changed the title chore(ci): bump socket-registry actions to 7ca50837 (tool-envs cascade) chore(ci): bump socket-registry actions to fd589015 (SOCKET_TOOL_CHECKSUMS_FILE) Apr 24, 2026
@jdalton John-David Dalton (jdalton) force-pushed the chore/registry-sha-bump-13684cd8 branch from 7487ab8 to 1287c5f Compare April 24, 2026 17:06
@jdalton John-David Dalton (jdalton) changed the title chore(ci): bump socket-registry actions to fd589015 (SOCKET_TOOL_CHECKSUMS_FILE) chore(ci): bump socket-registry actions to 444b6415 (scan auto-skip) Apr 24, 2026
…71e83f

The bumped socket-registry actions (Layer 1 commit 24ad6b61, surfaced
via Layer 3 propagation SHA 0371e83f) now enforce a runtime floor of
@socketsecurity/lib >= the latest npm-published version. The previous
pin (5.21.0) ships a stubbed pacote fetcher that throws inside
downloadPackage when the install action provisions ecc-agentshield.

Bumps the consumer pin to 5.24.0 (current npm latest) and re-pins
socket-registry refs to the 0371e83f propagation SHA in the same
commit so CI clears both gates simultaneously.
@socket-security
Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updated@​socketsecurity/​lib@​5.21.0 ⏵ 5.24.0100100100100100

View full report

@jdalton John-David Dalton (jdalton) merged commit 4c55477 into main Apr 24, 2026
11 checks passed
@jdalton John-David Dalton (jdalton) deleted the chore/registry-sha-bump-13684cd8 branch April 24, 2026 20:04
John-David Dalton (jdalton) added a commit that referenced this pull request Apr 24, 2026
…on fix) (#615)

The previous propagation SHA (0371e83f, merged via #611) 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, falling back to
the hardcoded floor (5.24.0) when the response isn't plain semver.
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