Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Plugin marketplace serves oldest version instead of latest when multiple submissions exist [1 comments, 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#45051•Fetched 2026-04-09 08:14:27
View on GitHub
Comments
1
Participants
1
Timeline
1
Reactions
0
Author
fdaviddptfdaviddpt
Participants
fdaviddptfdaviddpt
Timeline (top)
commented ×1

When a plugin is submitted multiple times to the Claude Code marketplace with the same name but different versions, `/plugin install` delivers the oldest version instead of the latest.

Root Cause

When a plugin is submitted multiple times to the Claude Code marketplace with the same name but different versions, `/plugin install` delivers the oldest version instead of the latest.

RAW_BUFFERClick to expand / collapse

Description

When a plugin is submitted multiple times to the Claude Code marketplace with the same name but different versions, `/plugin install` delivers the oldest version instead of the latest.

Steps to Reproduce

  1. Submit plugin `remember` v0.1.0 to the marketplace (March 15) → Published
  2. Submit plugin `remember` v0.4.0 to the marketplace (April 5) → Published
  3. All 3 submissions show "Published" in the Plugin submissions dashboard
  4. Run `/plugin install remember` in Claude Code

Expected Behavior

`/plugin install remember` should install v0.4.0 (the latest published version).

Actual Behavior

`/plugin install remember` installs v0.1.0 (the oldest version).

``` remember @ claude-plugins-official Version: 0.1.0 ```

Uninstalling and reinstalling does not help — still delivers v0.1.0.

Evidence

(Screenshot will be added as comment — needs manual upload to GitHub)

Plugin submissions dashboard shows 3 "Published" entries:

  • remember v0.4.0 — Published — 5 Apr 2026
  • remember (older) — Published — 30 Mar 2026
  • remember (oldest, v0.1.0) — Published — 15 Mar 2026

CLI proof

``` $ /plugin install remember ✓ Installed remember. Run /reload-plugins to activate.

$ /plugin remember @ claude-plugins-official Version: 0.1.0 Status: Enabled ```

Environment

Additional Context

The marketplace UI shows all 3 versions as "Published" rather than superseding older versions. It appears new submissions with the same plugin name create separate entries instead of updating the existing one, and the install resolver picks the first (oldest) entry.

extent analysis

TL;DR

The issue can be resolved by updating the plugin installation logic to prioritize the latest version of a plugin with the same name.

Guidance

  • The root cause of the issue seems to be the plugin installation logic, which currently picks the first (oldest) entry for a plugin with multiple versions.
  • To verify the issue, check the plugin submissions dashboard to ensure that all versions of the plugin are listed as "Published" and that the installation command is indeed installing the oldest version.
  • A potential workaround could be to modify the plugin installation command to accept a version parameter, allowing users to specify the version they want to install.
  • The marketplace UI should be updated to supersede older versions of a plugin instead of creating separate entries for each new submission.

Example

No code snippet is provided as the issue does not contain enough technical details to create a specific example.

Notes

The provided information suggests that the issue is related to the plugin installation logic and the marketplace UI. However, without more technical details, it is difficult to provide a comprehensive solution.

Recommendation

Apply workaround: Modify the plugin installation command to accept a version parameter, allowing users to specify the version they want to install. This will provide a temporary solution until the underlying issue with the plugin installation logic and marketplace UI can be resolved.

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…
#environment variable#network issue#logging issue#authentication issue#prompt issue

Still need to ship something?

×6

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

Back to top recommendations

TRENDING