Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Plugin version not respected

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Error Messages/Logs

Root Cause

Setting version pins the plugin. If plugin.json declares "version": "1.0.0", pushing new commits without changing that string does nothing for existing users, because Claude Code sees the same version and keeps the cached copy. Bump the field on every release, or omit it to use the commit SHA.

Fix Action

Fix / Workaround

I also tried some workarounds, like re-setting the version to 0.0.0 or "master" after doing a release, and it just pulls that instead, not respecting any semver rules whatsoever.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

I have a plugin (https://github.com/serpro69/claude-toolbox) which I version via plugin.json version field ( https://github.com/serpro69/claude-toolbox/blob/01406d4601bd9478d6984dcea6b8269f672dcfaf/klaude-plugin/.claude-plugin/plugin.json#L4 ) I noticed that some changes I pushed to a skill were picked up by the LLMs, even though they weren't released as a new version yet. I looked at the ~/.claude/plugin/marketplace and ~/.claude/plugin/cache , and the new changes were indeed there, under older version of the plugin.

Instead of respecting the plugin version, it always pulls master. This can be seen by both looking at the commit in the marketplace dir, as well as exploring the code in the cache dir.

I also tried some workarounds, like re-setting the version to 0.0.0 or "master" after doing a release, and it just pulls that instead, not respecting any semver rules whatsoever.

What Should Happen?

As per docs:

Setting version pins the plugin. If plugin.json declares "version": "1.0.0", pushing new commits without changing that string does nothing for existing users, because Claude Code sees the same version and keeps the cached copy. Bump the field on every release, or omit it to use the commit SHA.

Error Messages/Logs

Steps to Reproduce

  1. Release a new plugin version
  2. Make changes to the plugin (e.g. change a skill)
  3. claude plugin marketplace update in a project that uses the plugin
  4. Check the code in plugin marketplace and cache dirs in ~/.claude/plugins

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.150 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING