Repository navigation
Drop the reusable builder (stay at SLSA Build L2) - #40
Merged
Merged
Conversation
…fulciotest The release stays at SLSA Build L2: each repository's release.yml, dispatched on main, builds, signs and attests in one job, and its SAN binds the repository because nothing else can invoke that workflow. A reusable builder in the same job never gave L3 - the caller's code shares the job with the id-token - and a public one made the SAN callable from any repository. A dedicated builder repo with a separate signing job would, at the cost of moving every repository's publish into it; against whoever already holds main, it buys little. Reverts 3a12532, a38a073, defd29b, 19bcef5, 33b66d7 and 70a418a; with rekor gone from the graph, vulngate is clean at the previous grpc and x/net. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Decision 2026-10-13: the release stays at L2. Each repo's
release.ymlis dispatched on main and builds, signs and attests in one job; its SAN binds the repository because nothing else can invoke that workflow.A reusable builder in the same job never was L3, since the caller's
task releaseshares the job with the id-token. A public one also made the builder's SAN callable from any repository. Real L3 needs a dedicated builder repo with a separate signing job, and that means moving every repo's publish (GitHub release, oras, AMI registration, images PR) into it. Against an attacker who already holds main, it buys little.Reverts #36, #37, #38, #39 (Builder/Builders/Repository,
provenance -builder/BuiltBy,fulciotest). With rekor out of the graph, vulngate is clean at the previous grpc/x/net.task lintgreen.🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need.