Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix plugin.json silently overrides marketplace.json version with no warning [1 participants]

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…
GitHub stats
anthropics/claude-code#54280•Fetched 2026-04-29 06:31:33
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
nfrithnfrith
Participants
nfrithnfrith
Timeline (top)
labeled ×3

The version-resolution waterfall states plugin.json's version field wins over the marketplace entry's version field. The docs note this in a "Warning" callout but the platform does not surface any warning when both files declare a version. Plugin authors can set marketplace.json's version, expect it to take effect, and have it silently ignored.

Root Cause

The version-resolution waterfall states plugin.json's version field wins over the marketplace entry's version field. The docs note this in a "Warning" callout but the platform does not surface any warning when both files declare a version. Plugin authors can set marketplace.json's version, expect it to take effect, and have it silently ignored.

RAW_BUFFERClick to expand / collapse

Summary

The version-resolution waterfall states plugin.json's version field wins over the marketplace entry's version field. The docs note this in a "Warning" callout but the platform does not surface any warning when both files declare a version. Plugin authors can set marketplace.json's version, expect it to take effect, and have it silently ignored.

Reproduction

  1. Set plugin.json version: "0.1.0-beta.28"
  2. Set marketplace.json plugin entry version: "1.0.0"
  3. Install the plugin
  4. Customize panel shows Version: 0.1.0-beta.28 (plugin.json wins)

No warning anywhere — not at marketplace add, not at install, not in claude plugin validate output.

Real-world incident

The author of nfrith/als had plugin.json declaring 0.1.0-beta.28 and marketplace.json declaring 0.1.0-beta.1 for an unknown duration. The 0.1.0-beta.1 value did nothing, silently, until manually noticed during empirical testing. No warning was ever surfaced.

Expected

At minimum a warning when both files declare conflicting versions — at validation time, marketplace add, or in /plugins UI.

Actual

Silent. Plugin authors can be misled indefinitely.

Environment

Claude Code Desktop v2.1.121 / Claude Code CLI v2.1.121, macOS.

extent analysis

TL;DR

To avoid version conflicts, ensure that the version field in plugin.json and marketplace.json are identical, as plugin.json's version currently takes precedence.

Guidance

  • Verify that both plugin.json and marketplace.json have the same version field to avoid conflicts.
  • When updating the version, make sure to update it in both files to maintain consistency.
  • Consider adding a validation step in your development workflow to check for version consistency between the two files.
  • If a conflict is found, update the version field in plugin.json to match the intended version, as it takes precedence.

Example

No code snippet is provided as it's not necessary for this specific issue.

Notes

This solution assumes that the version conflict is the primary cause of the issue. It's also important to note that the platform should ideally surface a warning when both files declare conflicting versions, but until that's implemented, manual verification is necessary.

Recommendation

Apply workaround: Ensure version consistency between plugin.json and marketplace.json to avoid silent version conflicts, as the platform does not currently provide warnings for such conflicts.

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…
#mixed precision#training loop#device allocation#model download#tokenizer error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING