release: v0.5.0 — Apache-2.0, core@v0.8.0, reviewer@v0.3.0 - #32
Merged
Conversation
… v0.4.0 changelog entry
Signetry Reviewer — 🟣 Escalate to a designated reviewerEscalate to a designated reviewer — this PR touches security-sensitive surface (.github/workflows/reviewer.yml). No blocking issue was found automatically, but a human owner should sign off. Deterministic gates (the authority)
Findings (2, 0 blocking)
Sensitive surfaceThis PR changes security-sensitive paths that warrant a designated reviewer:
MergeA designated reviewer / code owner should sign off before merge (sensitive surface).
|
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.
Cuts Signetry Admission v0.5.0: the Apache-2.0 relicense,
signetry-core@v0.8.0,signetry-reviewer@v0.3.0.A release that was never written down
CHANGELOG.mdhad two sections under## [Unreleased], and only one of them wasactually unreleased.
### Changed — Signetry namingshipped in v0.4.0 on2026-08-12 — its own bullets pin
core@v0.6.0andreviewer@v0.1.2, versions thatpredate
main. It was sitting underUnreleasedtelling readers that the rename,the
signetryCLI, theSIGNETRY_*env prefix and the.signetry/admission.yamlcontract path had not shipped yet, while
@v1had been serving all of it for threeweeks.
So this splits them:
## [0.4.0] — 2026-08-12now holds the naming section (with the@v1move that the other release entries all record), and## [0.5.0]holds thelicensing change plus this release's pin bumps.
One stale claim corrected
MARKETPLACE.mdtold Marketplace readers to "Pin@v1(moving) or@v0.2.0(exact)" — two releases out of date, so anyone who followed it verbatim pinned an
Action from before the Signetry rename. It names
@v0.5.0now.Pins
action.ymldefault core installcore@v0.7.0core@v0.8.0reviewer@v0.2.0reviewer@v0.3.0The changelog is explicit that the pin was
@v0.6.0as ofv0.4.0and that anintermediate bump to
@v0.7.0(#30) landed onmainwithout a changelog entry —the gap is recorded rather than papered over.
Floors are deliberately left alone:
SECURITY.md's@v0.1.3+and thesignetry-core >= 0.5.0capability floors inaction.yml/MARKETPLACE.mdareminimums, not pins, and are still correct.