feat(release): add exact release evidence index contract - #217
Draft
seonghobae wants to merge 14 commits into
Draft
feat(release): add exact release evidence index contract#217seonghobae wants to merge 14 commits into
seonghobae wants to merge 14 commits into
Conversation
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Sep 2, 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.
Scope
Advances #210 with one bounded, machine-readable release-evidence contract. This does not close #210, publish a release candidate, or claim release readiness.
release-evidence.mjsbinds retained artifacts to one exact source commit, requires canonical SHA-256 evidence, keeps unresolved P0 buyer gaps explicit, requires SBOM/build-provenance/checksum/signature evidence, identifies SPDX 3.0.1 and SLSA provenance by their canonical identities, binds signatures structurally to retained subjects, and rejects duplicate/path-like/unknown/malformed evidence. Structural validation remains distinct from cryptographic signature verification and release acceptance.The original TDD lineage is preserved, including the RED that required signature evidence to bind a retained subject plus exact digest and the subsequent directory-boundary hardening. No certification, SLSA-level, installation, rollback or buyer-journey claim follows from this slice.
Protected-main adoption
The lane previously adopted #239 as
d8cda8a6c7d00ed31e73717fb290295176a350fc. Protected main then advanced through #240 tob84751674dd92bdcd0e266c7f002cdc43f5a938b, removing unsafe docs-only filters from CI and Commercial Readiness.Current exact head
e2965452ddb9227c5a0462a7820f95c70fe11821is a non-force two-parent descendant ofd8cda8a6...and current protected main. Its merge tree keeps #240's workflow semantics while preserving exactly the four release-evidence-owned paths. Fresh compare from protected main is ahead-only (behind_by=0) with those four paths only.No predecessor check/review evidence transfers after this head move. Exact-head repository and central gates remain authoritative; queued/absent/skipped evidence is not passing. Keep Draft until terminal exact-head validation, current review/thread policy, and unchanged-base compatibility are satisfied without bypass.
Refs #210.