Skip to content

chore(workflows): move the five image pins to what #88's build published - #89

Merged
garymike merged 1 commit into
mainfrom
chore/refresh-pins-after-86-87-88
Oct 21, 2026
Merged

garymike merged 1 commit into
mainfrom
chore/refresh-pins-after-86-87-88

Conversation

@garymike

Copy link
Copy Markdown
Owner

The first pin refresh prompted by the check rather than by someone remembering.

#88 added the pins job. Its own merge touched .github/workflows/build-toolbox.yml, which is in that workflow's trigger paths, so it rebuilt, the job ran, and it went red naming all five stale pins. A true positive on first firing, because #86 and #87 had already left them behind.

security-toolbox-base   d2f1d6b33d9c -> 9be060794ecb
gha-toolbox             7e6558f3b46c -> 4cef3443acbd
sast-toolbox            6bf6d9aafd5a -> edfd4db8752a
iac-toolbox             bc4198b93fcc -> 08e1338df20c
skill-audit-toolbox     c10bc17412a2 -> f5f99b96668f

Where the digests came from

The job's own annotations, which report steps.build.outputs.digest from the run that published them. Each annotation names the file, the stale pin and the digest to move to, so the refresh is mechanical:

skill-audit.yml pins skill-audit-toolbox@c10bc174… but this run published f5f99b96…. Move the pin alongside toolbox/tools.lock, per the comment in that workflow.

No local pull and no registry lookup, so neither the index-versus-manifest ambiguity that put two of five pins in wrong in #82, nor a hand-copied digest, can get in. I parsed the annotations and then cross-checked every pin against the published value.

Verified behind the new pins

Ran the images rather than trusting that a green build implies the right contents:

One limitation the check has, found by it happening

#86's build failed on a cosign/Rekor 409: "an equivalent entry already exists in the transparency log". toolbox/gha was unchanged, so gha-toolbox rebuilt to a byte-identical digest that had already been signed.

That is benign in itself, and incidentally proves the builds are reproducible when inputs do not change. But a failed domain arm skips the pins job rather than running it, so a reproducible rebuild can silence the check. The needs: [base, domain] wants an if: that tolerates a partial build, or the sign step wants to treat a 409 as success.

Not fixed here, because this PR should stay a pin refresh. Worth doing before the next time a tool bump touches only some images.

🤖 Generated with Claude Code

The first refresh prompted by the check rather than by remembering. #88 added
a `pins` job to build-toolbox.yml; its own merge triggered a rebuild, the job
ran, and it went red naming all five stale pins with the digest each should
move to. A true positive on first firing, because #86 and #87 had already left
them behind.

  security-toolbox-base   d2f1d6b33d9c -> 9be060794ecb
  gha-toolbox             7e6558f3b46c -> 4cef3443acbd
  sast-toolbox            6bf6d9aafd5a -> edfd4db8752a
  iac-toolbox             bc4198b93fcc -> 08e1338df20c
  skill-audit-toolbox     c10bc17412a2 -> f5f99b96668f

Digests taken from the job's own annotations, which report
steps.build.outputs.digest from the run that published them. No local pull and
no registry lookup, so neither the index-vs-manifest ambiguity from #82 nor a
hand-copied digest can get in.

Verified behind the new pins: base ships trufflehog 3.99.3, betterleaks 1.9.0,
osv-scanner 2.7.0 and syft 1.55.0, with pip 26.2.2 vendoring certifi
2026.10.19, so #87's CVE fix is actually in what callers now get.
skill-audit ships SkillSpector v2.13.0.

One thing the check cannot currently survive: #86's build failed on a
cosign/Rekor 409, "an equivalent entry already exists in the transparency
log", because toolbox/gha was unchanged so gha-toolbox rebuilt to a byte
identical digest that was already signed. A failed domain arm skips the pins
job rather than running it. Benign cause, but it means a reproducible rebuild
can silence the check. Noted, not fixed here.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@garymike
garymike merged commit ceaa563 into main Oct 21, 2026
9 checks passed
@garymike
garymike deleted the chore/refresh-pins-after-86-87-88 branch October 21, 2026 18:26
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