Plugin manifest still at 0.0.8 while 0.0.9 is advertised

[crsmoore]

Summary

The 0.0.9 release is advertised but isn't actually installable.

latest.json and package.json are at 0.0.9, but the plugin manifest plugin/.claude-plugin/plugin.json is still 0.0.8 on main.

Claude Code resolves the installable version from the manifest, so /plugin install supermemory@supermemory-plugins resolves to 0.0.8, sees it's already installed, and does nothing.

Impact: Users get a persistent "v0.0.9 available" update notice that no update action can ever satisfy, because there's no 0.0.9 manifest to install.

Steps to reproduce

1. On an up-to-date marketplace clone, run /plugin marketplace update supermemory-plugins.
2. Run /plugin install supermemory@supermemory-plugins.
3. Plugin stays at 0.0.8; the "0.0.9 available" notice persists.

Evidence (current main, commit dd805f4)

• latest.json → "version": "0.0.9"
• package.json → "version": "0.0.9"
• plugin/.claude-plugin/plugin.json → "version": "0.0.8" ← not bumped

Commit 178acc2 ("Bump plugin version to 0.0.9") updated package.json and latest.json but missed the plugin manifest.

Fix

Bump version in plugin/.claude-plugin/plugin.json to 0.0.9 to match (and tag the release, if that's part of your flow).

[selimdev00]

Same thing has now happened again with 0.0.10.

Current main (commit 42cc164):

• latest.json -> "version": "0.0.10"
• plugin/.claude-plugin/plugin.json -> "version": "0.0.9"
• package.json -> "version": "0.0.9"

So the update hook fetches latest.json, sees 0.0.10, and shows the update notice every session, but /plugin marketplace update + /plugin install supermemory@supermemory-plugins can only ever install 0.0.9. The notice is unsatisfiable again.

This time even package.json wasn't bumped, only latest.json. Maybe worth a CI check that fails when latest.json version doesn't match the plugin manifest, since this is the second release in a row with this mismatch.

[cameronapak]

Yep. i'm running into that same issue ^

[karljamoralin]

Running into this same issue as well

[cameronapak]

I am contemplating dropping paid Supermemory plan and Claude integration. Please, please fix this @Dhravya

[skalingclouds]

Also hitting the 0.0.9 → phantom 0.0.10 recurrence (same state @selimdev00 reported: main @ 42cc164, latest.json = 0.0.10, plugin/.claude-plugin/plugin.json = 0.0.9, and no 0.0.10 tag or release exists).

One extra root-cause detail for anyone debugging: the version the update check compares isn't read from the manifest at runtime — it's bundled into the hook script at build time. scripts/context-hook.cjs contains a hard-coded PLUGIN_VERSION of "0.0.9" and fetches https://raw.githubusercontent.com/supermemoryai/claude-supermemory/main/latest.json, so the notice fires every session whenever latest.json is ahead of the last actually-shipped build — which is exactly the state main is in now.

Temporary workaround until a real 0.0.10 ships — patch the cached copy so the comparison passes:

# macOS (on Linux: sed -i 's/.../.../' ...)
sed -i '' 's/"0\.0\.9"/"0.0.10"/' ~/.claude/plugins/cache/supermemory-plugins/supermemory/0.0.9/scripts/context-hook.cjs

Verified: the update notice stops immediately. It's also self-healing — the cached file is replaced when the next real release installs, so genuine update notices keep working.

+1 to the CI suggestion upthread: a release check that fails when latest.json is ahead of plugin/.claude-plugin/plugin.json would stop this third recurrence (#23, #43/#69, now 0.0.10) from becoming a fourth.