Repository navigation
chore(workflows): move the five image pins to what 976ef61's build published - #104
Merged
Merged
Conversation
…blished The follow-up half of #103, and it covers #102 as well: both landed toolbox changes without moving a pin, so callers have been resolving images built before the nine-tool bump. For skill-audit-toolbox that gap was load-bearing, because #103's docs assert v2.13.4 numbers while the pinned image still carried v2.13.2. Permitted rather than forced. check-image-pins.py reported all 5 of 5 behind before the move, which is the state the mover's guard requires, so no --force was needed: gha-security.yml inputs 5c137c684483 -> f6a4a72e874a iac-security.yml inputs f24b2cabd9b1 -> 4a28bbf3e20f sast.yml inputs de509bd1ace1 -> 547b6bc2feaf security-scan.yml inputs 2aed68cf9f33 -> b4802091e180 skill-audit.yml inputs b011e83c21f6 -> a36fc4fa94cf Verified the usual way: each digest resolved from the per-commit sha-976ef61d7b38 tag rather than latest, and its build-inputs label read back out of the registry and compared with the fingerprint this repo computes now. All five matched before anything was written. check-image-pins.py now reports all five current. Verified one step further, because this is the pin #103's claims rest on. Pulled the skill-audit-toolbox digest callers will now resolve and ran the proof against it, not against a locally built image: SkillSpector v2.13.4, semgrep 1.184.0 gate-proof.sh: 16 of 16 gecko-demo 64/100 exit 1, BLOCKS gecko-hook-demo 76/100 exit 1, BLOCKS config-injection-demo 100/100 exit 1, BLOCKS sibling-config-demo 51/100 exit 1, BLOCKS memory-poisoning-demo 27/100 exit 0, does NOT block The 27/100 in README.md and docs/ is now what a caller resolving this pin actually gets.
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
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.
The follow-up half of #103, and it covers #102 as well: both landed toolbox changes without moving a pin, so callers have been resolving images built before the nine-tool bump. For
skill-audit-toolboxthat gap was load-bearing, because #103's docs assert v2.13.4 numbers while the pinned image still carried v2.13.2.Permitted, not forced
check-image-pins.pyreported all 5 of 5 behind before the move, which is the state the mover's guard requires, so no--forcewas needed.gha-security.yml5c137c684483f6a4a72e874aiac-security.ymlf24b2cabd9b14a28bbf3e20fsast.ymlde509bd1ace1547b6bc2feafsecurity-scan.yml2aed68cf9f33b4802091e180skill-audit.ymlb011e83c21f6a36fc4fa94cfEach digest was resolved from the per-commit
sha-976ef61d7b38tag rather thanlatest, and itsbuild-inputslabel read back out of the registry and compared with the fingerprint this repo computes now. All five matched before anything was written.check-image-pins.pynow reports all five current.Verified against the pinned digest, not a local build
This is the pin #103's claims rest on, so the proof ran against the image a caller will actually resolve:
The
27/100inREADME.mdanddocs/is now what a caller resolving this pin gets.