release: v0.3.0 — Apache-2.0, core@v0.8.0, and the 404 install path fixed - #20
Merged
Conversation
Contributor
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 (1, 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 plugins v0.3.0 — the first release since
0.2.2(2026-07-23), andthe one that makes the repo consumable again.
Everything under
## [Unreleased]has been sitting there for six weeks: theUmbra → Signetry rebrand, the Apache-2.0 relicense, a 60-second quickstart in every
integration README (two of which did not exist), the community-health files, and the
404 install-path fix. That last one is why this release matters more than the
version number suggests:
README.mdtold Claude Code users to run/plugin marketplace add bkd-dotcom/signetry-plugins, a repository that has notexisted since the org move — so the documented primary install path for the plugin
could not work, and the fix was unreleased.
0.2.2→0.3.0in both places that declare a version:.claude-plugin/marketplace.json(metadata.version) andclaude-code/signetry/.claude-plugin/plugin.json.Pins
signetry-core(15 sites, 13 files)core@v0.7.0core@v0.8.0reviewer@v0.2.0reviewer@v0.3.0rev:(.pre-commit-hooks.yaml,universal/README.md)v0.2.2v0.3.0The changelog's own pin bullet said the delta was
v0.6.0→v0.7.0. Since none ofit ever shipped, the delta an adopter actually gets is
v0.6.0→v0.8.0, and thebullet now says that — a changelog entry describes the release it is in, not the
commit that happened to write it.
One line of the record was destroyed by a find-and-replace
The rename section was headed:
The global rebrand swept its own history, overwriting the from side of the arrow and
leaving a heading that states nothing. The old name was Umbra
(
b313699 feat: Umbra editor/agent plugins), so it now readsrebranded Umbra → Signetry. The bullets below it are left alone — they describe whateach thing is called now, which is still accurate.