claude plugins update doesn't pull marketplace repo, silently serves stale versions
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 15/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- typescript
Research direction
The report says marketplace freshness is checked by Claude Code CLI logic and may need to be reported to Anthropic; it does not identify a relevant file or test in this repository. Start by checking whether this repository contains the claude plugins update implementation. Done means the update flow fetches the remote marketplace before comparing versions, or the issue is confirmed as an upstream CLI bug and directed to the appropriate project.
Written by the indexing model from the issue text.
Description
Bug
claude plugins update compound-engineering@every-marketplace reports the plugin is "already at the latest version" when it isn't. In this case, it reported 2.30.0 as latest when the actual latest is 2.36.4.
Root Cause
The marketplace is stored as a local git clone at ~/.claude/plugins/marketplaces/every-marketplace/. The update command checks versions against this local clone but never pulls from the remote. So users who installed the marketplace before newer versions were published are silently stuck.
Reproduction
# Shows stale version as "latest"
claude plugins update compound-engineering@every-marketplace
# → "compound-engineering is already at the latest version (2.30.0)"
# Local clone is behind
git -C ~/.claude/plugins/marketplaces/every-marketplace/ log --oneline -1
# → e4ff6a8 [2.30.0]
# Manual pull fixes it
git -C ~/.claude/plugins/marketplaces/every-marketplace/ pull
Impact
Affects all users whose marketplace clone predates the latest release. They get no indication that they're behind — update tells them they're current.
Notes
This may be a Claude Code CLI issue rather than a plugin issue — the update command's marketplace-checking logic lives in the CLI, not the plugin. Filing here for visibility since this is where affected users will look. May also warrant reporting to Anthropic.
Workaround
git -C ~/.claude/plugins/marketplaces/every-marketplace/ pull
claude plugins update compound-engineering@every-marketplace
- Dominant language
- TypeScript
- Stars
- 25.6k
- Forks
- 2.1k
- Avg merge
- 3h 57m
- Merged PRs (30d)
- 170
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from EveryInc/compound-engineering-plugin
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EveryInc/compound-engineering-plugin#2085 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
EveryInc/compound-engineering-plugin#795 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 80/100
EveryInc/compound-engineering-plugin#2084 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
EveryInc/compound-engineering-plugin#2083 ·
Maintainers usually reply within 1 day
-
Host support: DeepSeek Harness (dsh)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 48/100
EveryInc/compound-engineering-plugin#2072 ·
Maintainers usually reply within 1 day
All issues in EveryInc/compound-engineering-plugin
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
hurttlocker/o8#6535 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
area: backend bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
snapotter-hq/SnapOtter#4856 ·
Maintainers usually reply within 1 day
-
bug follow-up
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
spellshift/realm#2509 ·
Maintainers usually reply within 1 day