Component
Plugin
Description
Summary
The release bump in #6800 (chore(release): bump SDK, CLI, and plugin versions, commit 1112be3) updated the two marketplace manifests but not the plugin manifests they point at:
.claude-plugin/marketplace.json "version": "0.2.14"
.cursor-plugin/marketplace.json "version": "0.2.14"
integrations/mem0-plugin/.claude-plugin/plugin.json "version": "0.2.13"
integrations/mem0-plugin/.cursor-plugin/plugin.json "version": "0.2.13"
integrations/mem0-plugin/.codex-plugin/plugin.json "version": "0.2.13"
The diff of 1112be3 shows the omission directly — it touched .claude-plugin/marketplace.json and .cursor-plugin/marketplace.json (0.2.13 → 0.2.14) and integrations/mem0-plugin/plugin.json (0.1.5 → 0.1.6, the Antigravity manifest), but none of the three per-host plugin.json files.
This is a regression, not a convention: git log -p on the two files shows they moved in lockstep through 0.2.9, 0.2.10, 0.2.11, 0.2.12 and 0.2.13. 0.2.14 is the first release where they diverge.
Both marketplace entries point at the same directory ("source": "./integrations/mem0-plugin"), so a host that lists 0.2.14 as available will install a plugin whose own manifest reports 0.2.13 — the version never converges, "update available" does not clear, and any support triage that asks a user for their installed plugin version gets a number that does not exist in the marketplace.
Steps to Reproduce
# From a clone of main:
import json
marketplace = json.load(open(".claude-plugin/marketplace.json"))
plugin = json.load(open("integrations/mem0-plugin/.claude-plugin/plugin.json"))
print("marketplace advertises:", marketplace["plugins"][0]["version"])
print("plugin.json declares :", plugin["version"])
assert marketplace["plugins"][0]["version"] == plugin["version"]
Equivalently, from a shell:
$ grep '"version"' .claude-plugin/marketplace.json
"version": "0.2.14"
$ grep '"version"' integrations/mem0-plugin/.claude-plugin/plugin.json
"version": "0.2.13",
Expected Behavior
.claude-plugin/marketplace.json, .cursor-plugin/marketplace.json, and the three integrations/mem0-plugin/.{claude,cursor,codex}-plugin/plugin.json manifests all declare the same version for the same released artifact — as they did for every release up to 0.2.13. Ideally a CI check (or the release script) asserts this, since the manifests are duplicated across five files.
Actual Behavior
marketplace advertises: 0.2.14
plugin.json declares : 0.2.13
AssertionError
The Codex plugin manifest is at 0.2.13 as well, and the root marketplace.json / .codex-plugin/marketplace.json carry no version at all, so there is nothing that pins the released version to what the plugin reports.
Environment
- mem0 version: 2.0.17 (
main @ 12c47f5); mem0 plugin 0.2.13 / marketplace 0.2.14
- Python/Node version: N/A (static manifests)
- OS: N/A (platform independent)
Component
Plugin
Description
Summary
The release bump in #6800 (
chore(release): bump SDK, CLI, and plugin versions, commit 1112be3) updated the two marketplace manifests but not the plugin manifests they point at:The diff of 1112be3 shows the omission directly — it touched
.claude-plugin/marketplace.jsonand.cursor-plugin/marketplace.json(0.2.13 → 0.2.14) andintegrations/mem0-plugin/plugin.json(0.1.5 → 0.1.6, the Antigravity manifest), but none of the three per-hostplugin.jsonfiles.This is a regression, not a convention:
git log -pon the two files shows they moved in lockstep through 0.2.9, 0.2.10, 0.2.11, 0.2.12 and 0.2.13. 0.2.14 is the first release where they diverge.Both marketplace entries point at the same directory (
"source": "./integrations/mem0-plugin"), so a host that lists 0.2.14 as available will install a plugin whose own manifest reports 0.2.13 — the version never converges, "update available" does not clear, and any support triage that asks a user for their installed plugin version gets a number that does not exist in the marketplace.Steps to Reproduce
Equivalently, from a shell:
Expected Behavior
.claude-plugin/marketplace.json,.cursor-plugin/marketplace.json, and the threeintegrations/mem0-plugin/.{claude,cursor,codex}-plugin/plugin.jsonmanifests all declare the same version for the same released artifact — as they did for every release up to 0.2.13. Ideally a CI check (or the release script) asserts this, since the manifests are duplicated across five files.Actual Behavior
The Codex plugin manifest is at 0.2.13 as well, and the root
marketplace.json/.codex-plugin/marketplace.jsoncarry no version at all, so there is nothing that pins the released version to what the plugin reports.Environment
main@ 12c47f5); mem0 plugin 0.2.13 / marketplace 0.2.14