Repository navigation
S5: release through a reusable builder; daily OSV scan - #109
Merged
Merged
Conversation
…ly OSV scan release.yml publishes nothing itself: it calls build-release.yml (on: workflow_call alone), which builds, signs, attests, tags and publishes. Every certificate then names the builder, so the identity a file is checked against is build-release.yml@refs/heads/main, and the provenance's builder.id says the same (go tool provenance -builder); externalParameters.workflow stays release.yml, what was dispatched. workflows_test holds it with attestgate's Builder. The builder runs on ubuntu-24.04 with an empty BuildKit and no cache read: a Blacksmith certificate reads self-hosted, and main's lane cache is an input no pin holds. The cost is a cold build each release; the bytes are the same. osv.yml runs task osv daily: the newest release's SBOM, its signature checked against the builder, scanned with osv-scanner (pinned in versions.yaml), and one issue per finding, by title, ever. go-tools a38a073. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This was referenced Oct 13, 2026
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.
S5 for spin-machine.
release.yml(dispatch on main) publishes nothing: it callsbuild-release.yml(on: workflow_callalone), which holds the old release job: build, fingerprint-diff/notes, provenance, sign/attest/verify, tag, publish. The certificate names the builder, so the identity is nowhttps://github.com/spin-stack/spin-machine/.github/workflows/build-release.yml@refs/heads/main.go tool provenance -buildermakesbuilder.idsay the same;externalParameters.workflowstaysrelease.yml.workflows_testsets attestgate'sBuilder(planted: pointing it at release.yml fails on both rules).ubuntu-24.04with an emptydocker-containerBuildKit, reading no cache (no Blacksmith sticky disk, notype=ghascopes). Blacksmith's certificate reads self-hosted, and main's lane cache is an input no pin holds. This was a fork the plan left open ("cache dropped or named as resolvedDependencies"). I chose to drop the cache: each release compiles QEMU, the kernel and the image from cold (timeout 300 min). The builds are reproducible, so the bytes do not change; hack/fingerprint-diff reports it if they ever do. A "Make room on the disk" step frees the runner's unused toolchains.task osvdownloads the newest release's.cdx.json, checks its signature against the builder identity, runs osv-scanner (newversions.yamlentry, v2.7.0, viago runlike actionlint), and writes_output/osv.tsv. The workflow opens one issue per finding, matched by exact title across open and closed issues, so a closed finding is never reopened. Checked: osv-scanner v2.7.0 reads go-tools' nested CycloneDX (171 packages from spin-term's) and the jq extraction.Flag day: spin's
release.Machineidentity has to move tobuild-release.ymlbefore spin takes the first machine release cut through this; that change follows in spin. No machine release from main exists yet, so nothing verifies in between.task lint,task testgreen;task mutate: no Go outside tests.🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need.