Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Marketplace auto-update fetches but doesn't pull, so plugin updates never apply [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#49410•Fetched 2026-04-17 08:41:56
View on GitHub
Comments
1
Participants
1
Timeline
6
Reactions
0
Author
ch-davidriottch-davidriott
Participants
ch-davidriottch-davidriott
Timeline (top)
labeled ×4closed ×1commented ×1

Enabling "auto-update" on a marketplace doesn't actually apply updates. The marketplace repo is fetched (git fetch) but never merged/pulled, so the local checkout stays stale. Version bumps in marketplace.json are never seen locally, and plugin updates never propagate.

Root Cause

Enabling "auto-update" on a marketplace doesn't actually apply updates. The marketplace repo is fetched (git fetch) but never merged/pulled, so the local checkout stays stale. Version bumps in marketplace.json are never seen locally, and plugin updates never propagate.

Fix Action

Workaround

Users must manually run:

/plugin marketplace update <name>
/reload-plugins

This does a proper pull and applies the update. But it defeats the purpose of "Enable auto-update."

Code Example

local HEAD:       <old commit>   (version 1.0.0)
origin/main:      <new commit>   (version 1.1.0)

---

/plugin marketplace update <name>
/reload-plugins
RAW_BUFFERClick to expand / collapse

Summary

Enabling "auto-update" on a marketplace doesn't actually apply updates. The marketplace repo is fetched (git fetch) but never merged/pulled, so the local checkout stays stale. Version bumps in marketplace.json are never seen locally, and plugin updates never propagate.

Steps to reproduce

  1. Create a plugin marketplace repo on GitHub with a plugin at version 1.0.0
  2. Install: /plugin marketplace add org/repo → /plugin install plugin-name@marketplace-name
  3. Confirm plugin works
  4. Push a change to the plugin repo: add a new skill, bump version to 1.1.0 in both plugin.json and marketplace.json
  5. Enable auto-update: /plugin → Marketplaces → select marketplace → Enable auto-update
  6. Start a new session

Expected: Plugin updates to 1.1.0, new skill is available
Actual: Plugin stays at 1.0.0, new skill is not available

Diagnosis

The marketplace clone at ~/.claude/plugins/marketplaces/<name>/ shows:

local HEAD:       <old commit>   (version 1.0.0)
origin/main:      <new commit>   (version 1.1.0)

git fetch runs, but the working tree is never updated. Since Claude Code reads marketplace.json from the working tree (not from origin/main), it never sees the version bump.

Workaround

Users must manually run:

/plugin marketplace update <name>
/reload-plugins

This does a proper pull and applies the update. But it defeats the purpose of "Enable auto-update."

Environment

  • Claude Code CLI (latest as of 2026-04-16)
  • macOS
  • Tested with a GitHub-hosted private marketplace repo
  • Also confirmed that superpowers-marketplace has the same local/remote divergence (local HEAD behind origin/main), suggesting this affects all third-party marketplaces

extent analysis

TL;DR

The most likely fix is to modify the auto-update mechanism to perform a git pull instead of just git fetch to update the local marketplace repository.

Guidance

  • The issue is caused by the auto-update feature only running git fetch but not merging or pulling the changes, resulting in a stale local checkout.
  • To verify the issue, check the marketplace clone at ~/.claude/plugins/marketplaces/<name>/ to see if the local HEAD is behind the origin/main branch.
  • A potential workaround is to run /plugin marketplace update <name> and /reload-plugins manually, but this defeats the purpose of auto-update.
  • The fix should involve modifying the auto-update script to perform a git pull to update the local repository.

Example

# Current auto-update script (hypothetical)
git fetch

# Proposed fix
git fetch
git pull origin main

Note: The actual implementation may vary depending on the scripting language and framework used.

Notes

The issue seems to affect all third-party marketplaces, and the proposed fix should be applied to the auto-update mechanism to ensure that the local marketplace repository is updated correctly.

Recommendation

Apply workaround: Run /plugin marketplace update <name> and /reload-plugins manually until a proper fix is implemented, as it provides a temporary solution to update the plugin to the latest version.

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…
#retriever error#indexing error#inference speed#output truncation#response parsing

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Marketplace auto-update fetches but doesn't pull, so plugin updates never apply [1 comments, 1 participants]