docs(security,ci): fix stale references and clarify stable-only release trigger#15
Merged
Merged
Conversation
…se trigger
- SECURITY.md: make the supported-version row version-agnostic ("latest
numeric release tag") so it no longer drifts every release (was a stale
"2.0.2").
- .github/workflows/README.md: correct the shared-CI pin (0.5.1/ac4d1f4 ->
0.8.1/8b8e3ea) and note the minimal runtime bundle as the second attested
release asset.
- release.yml: document that the numeric trigger is intentionally stable-only
(prerelease tags stay ruleset-protected but are cut manually, as the shared
workflow has no prerelease marking).
- Regenerate build/release-evidence.json for the new content digest, bound to
the current harness commit 04ad9fed (also clears the prior evidence.harness
lineage lag).
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.
Cleanup pass — no behavior change to the enforced release path.
2.0.2; made it version-agnostic (latest numeric release tag) so it never drifts again.0.5.1/ac4d1f4→0.8.1/8b8e3ea) and documented the minimal runtime bundle as the second attested release asset.build/release-evidence.jsonfor the new content digest, now bound to the current harness commit04ad9fed.Verified locally: actionlint clean, tag-time evidence verifier recompute +
emit_evidence --checkvalid.