Skip to content

Back to one release workflow (L2); the daily OSV scan stays - #111

Merged
aledbf merged 1 commit into
mainfrom
back-to-l2
Oct 13, 2026
Merged

aledbf merged 1 commit into
mainfrom
back-to-l2

Conversation

@aledbf

@aledbf aledbf commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

Decision 2026-10-13: the release stays at SLSA Build L2.

task lint, versions and workflows tests green.

🤖 Generated with Claude Code


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.

release.yml, dispatched on main, builds, signs, attests and publishes in one
job again, on its Blacksmith runner reading main's BuildKit cache, and its SAN
is release.yml@refs/heads/main: nothing but this repository's main can invoke
it, so the SAN binds the repository. The reusable builder never made the
release L3 - task release shared the job with the id-token - and being callable
from any repository it needed a guard and a pinned source repository to stay as
safe as before.

osv.yml and task osv stay, now checking the SBOM's signature against
release.yml@refs/heads/main. go-tools back at 99d7447.

Reverts f033995 and b207bee but for the OSV scan.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@aledbf
aledbf merged commit 302ced2 into main Oct 13, 2026
7 checks passed
@aledbf
aledbf deleted the back-to-l2 branch October 13, 2026 17:58
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