fix(plugin): bump both plugins to 0.2.0 so installs actually update - #333
Merged
Conversation
Claude Code only pulls a new copy of a plugin when the plugin's own version moves: "If set, users only receive updates when you bump this field." https://code.claude.com/docs/en/plugins-reference#version-management Both plugins have sat at 0.1.0 since they were created, through every change since — including v0.29.2, which rewrote every command file to carry the namespaced names. An existing install has been serving the old copy the whole time, so the surface people were told to use is the surface they did not get. Shipping a moshcode release does not carry plugin edits; only this number does. Both go to 0.2.0. The content they describe changed; the version now says so. To stop it happening again, `version` joins the catalog next to `commands` — the thing an editor is already touching when they change a plugin — with the mechanism spelled out above it, and a test pinning the catalog to the manifest that actually ships. Verified the guard fails when the two disagree rather than merely passing today. The README now documents `claude plugin update <plugin>@moshcode`, which is the step users need and the one nothing mentioned: `moshcode upgrade` updates the CLI and leaves installed plugins exactly where they were. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ThreatCrush Security Scan91 finding(s) HIGH/CRITICAL: 2 | MEDIUM: 41 | LOW: 48
…and 41 more. Full results in the Security tab. Snippets are redacted; ThreatCrush never prints matched credential material. |
Merged
ralyodio
added a commit
that referenced
this pull request
Aug 9, 2026
Bump to v0.29.3, releasing the plugin version bump (#333). Patch, and the moshcode half of it changes nothing: a README paragraph and a catalog field. The part that matters is in the plugins, which now declare 0.2.0 instead of the 0.1.0 they had carried since creation — the number an engine actually consults before pulling a new copy. Until now, every plugin edit shipped in a moshcode release reached new installs only. v0.29.2 rewrote every command file to carry the namespaced names, and no existing install saw it. This is the release that makes those edits reachable, via `claude plugin update <plugin>@moshcode`. Co-authored-by: Claude Opus 5 (1M context) <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
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.
Claude Code only pulls a new copy of a plugin when the plugin's own version moves:
Both plugins have sat at
0.1.0since they were created, through every change since — including v0.29.2, which rewrote every command file to carry the namespaced names. An existing install has been serving the old copy the whole time, so the surface people were told to use is the surface they didn't get. Shipping a moshcode release doesn't carry plugin edits; only this number does.Both go to 0.2.0. The content they describe changed; the version now says so.
Stopping it happening again
versionjoins the catalog insrc/plugins.mjsright next tocommands— the thing an editor is already touching when they change a plugin — with the mechanism spelled out above it, and a test pinning the catalog to the manifest that ships.I verified the guard fails when the two disagree rather than merely passing today:
Also documented
claude plugin update <plugin>@moshcode— the step users need and the one nothing mentioned.moshcode upgradeupdates the CLI and leaves installed plugins exactly where they were, which is not obvious.Verification
Full suite: 1388 tests, 0 failures.
🤖 Generated with Claude Code