Repository navigation
release: v1.1.0 — Ledger Gate - #44
Merged
Merged
Conversation
Bump every version surface from 1.0.0 to 1.1.0: package.json, both .claude-plugin manifests (three fields) and .codex-plugin/plugin.json, plus the README's `ratchet --version` example. Cut [Unreleased] into [1.1.0] - 2026-10-27 and add its compare link. Claude Code updates an installed plugin only when its version changes. While the version stayed at 1.0.0, `claude plugin update` reported "already at the latest version" and installs stayed on the 2026-07-30 build. That build lacked the MCP handshake fix (#43) and the store-split fix (#42). npm test passes all 16 suites. `ratchet --version` and `ratchet-evolve --version` print 1.1.0. `claude plugin validate` passes, with two warnings that predate this change. Co-Authored-By: Claude Opus 5.5 <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
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.
Why
Claude Code updates an installed plugin only when its version string changes.
mainhas moved a long way since 1.0.0, but every surface still said1.0.0. Soclaude plugin update ratchet@torque-loopreplied "already at the latest version (1.0.0)", and installs stayed on the 2026-07-30 build, without these fixes:torque;What
Version 1.0.0 → 1.1.0 on every surface
plugin-shapepins:package.json;.claude-plugin/plugin.json;.claude-plugin/marketplace.json(metadata and plugin entry);.codex-plugin/plugin.json;ratchet --versionexample.CHANGELOG:
[Unreleased]is cut to## [1.1.0] - 2026-10-27 — Ledger Gate;[1.1.0]compare link is added;[Unreleased]now compares fromv1.1.0.Why a minor version. Unreleased adds a tool (
ledger.update) and fixes. The one behaviour change is that stores under$CLAUDE_PLUGIN_DATAare no longer read. It is documented,RATCHET_DATA_DIRgives a way out, and no command is removed.The name "Ledger Gate" follows the release series and is easy to change.
Proof
npm test: all 16 suites pass, including "versions are aligned across every surface" and the README readout check.ratchet --version→ratchet 1.1.0;ratchet-evolve --version→ratchet-evolve 1.1.0.claude plugin validate .passes, with two warnings that predate this change: a rootCLAUDE.mdthe plugin does not load, and no listing icon.Not in this PR
v0.6.0, so the existing compare links for 0.7.0 to 1.0.0, and the new 1.1.0 one, point at tags that do not exist yet.claude plugin marketplace update torque-loopfollowed byclaude plugin update ratchet@torque-loopshould pick up 1.1.0. Run that to confirm.🤖 Generated with Claude Code