Skip to content

chore(workflows): move the five image pins to what 83a3172's build published - #97

Merged
garymike merged 1 commit into
mainfrom
chore/move-pins-83a3172
Oct 30, 2026
Merged

garymike merged 1 commit into
mainfrom
chore/move-pins-83a3172

Conversation

@garymike

Copy link
Copy Markdown
Owner

The second half of #96. Until this lands, callers are still scanning with the pre-#96 toolchain.

image was now
security-toolbox-base 4d1337450ff0 f6964aa2a12a
gha-toolbox 9df49b1d2c2b aa9916df163c
sast-toolbox bdbbdabc07eb bf29784b2121
iac-toolbox 98d329b49e54 e61590613c79
skill-audit-toolbox 161cbe2cb220 efe95ac44558

This is what actually delivers snyk-agent-scan 0.6.10, semgrep 1.183.0, checkov 3.4.0 and skillspector 2.13.2 to every repo consuming these workflows.

Verified before writing

Each digest came from resolving <image>:sha-83a3172ac5dd, not latest. latest is whichever push landed last, and two concurrent build runs have already raced it once (#91 and #93 started 25 seconds apart, and for iac-toolbox the earlier run's push won). build-toolbox.yml still has no concurrency: guard.

For every image, the resolved digest's io.github.garymike.toolbox.build-inputs label was read back out of the registry and compared with the fingerprint this repo computes now. Nothing would have been written if any of the five disagreed.

  gha-security.yml: gha-toolbox pin is current (inputs 4c17012a703d)
  iac-security.yml: iac-toolbox pin is current (inputs 595da26f5fda)
  sast.yml: sast-toolbox pin is current (inputs 925c60b58a19)
  security-scan.yml: security-toolbox-base pin is current (inputs df5477757fff)
  skill-audit.yml: skill-audit-toolbox pin is current (inputs 624bb0117cb8)

All 5 reusable-workflow image pins were built from the current repo inputs.

Those five fingerprints are the same values the Image pins run on 83a3172 reported as the repo's current inputs, so the local move and the CI check agree from independent directions.

…blished

The second half of #96's drift bump, so callers get snyk-agent-scan 0.6.10, semgrep 1.183.0,
checkov 3.4.0 and skillspector 2.13.2 rather than the previous toolchain.

Resolved from each image's `sha-83a3172ac5dd` tag rather than `latest`, because `latest` is
whichever push landed last and two concurrent build runs have already raced it once.
build-toolbox.yml still has no concurrency guard.

Every digest was verified before being written: its build-inputs label was read back from the
registry and compared with the fingerprint this repo computes now, and nothing would have been
written if any of the five disagreed. The five stamps also match what the Image pins run on
83a3172 reported as the repo's current inputs, so two independent sources agree.
scripts/check-image-pins.py now reports all five current.
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.

1 participant