From c1aef113d8a24ff74a32b1b79f004ed07c8acf0a Mon Sep 17 00:00:00 2001 From: Florian DAVID Date: Tue, 6 Oct 2026 15:06:26 +0200 Subject: [PATCH] fix: the marketplace release step requires a merge, not an open PR (#457) v0.13.0 through v0.16.0 shipped the claude-jit-context -> jit-context rename while the matching claude-marketplace rename PR (#5 there) sat open. Both the README install command and the #452 CHANGELOG claim about the renames map were false for the whole gap -- confirmed still live: that PR is still OPEN today. release.md's marketplace checklist step now says merging the PR is the gate, not opening it, names the live check to run before tagging, and points at issue 457 as the precedent. Co-Authored-By: Claude Sonnet 5 --- .claude/jit-context/paths/00-manual/release.md | 2 +- changelog.d/457.fixed.release-marketplace-merge-gate.md | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) create mode 100644 changelog.d/457.fixed.release-marketplace-merge-gate.md diff --git a/.claude/jit-context/paths/00-manual/release.md b/.claude/jit-context/paths/00-manual/release.md index c3ae88f..c9da03f 100644 --- a/.claude/jit-context/paths/00-manual/release.md +++ b/.claude/jit-context/paths/00-manual/release.md @@ -52,6 +52,6 @@ gh release create v0.2.0 --title "..." --notes "..." 2. **Validate the release tree in the portal before the tag.** Build it from the release commit, push it to a throwaway `release-preview` branch, validate `Digital-Process-Tools/claude-jit-context@release-preview` without clicking Next, delete the branch. The listing auto-publishes from a push webhook since 2026-10-04: the tag reaches the directory in minutes and no one looks first. `docs/releasing.md` step 3 has why. 3. **Tag, then push the tag** — `git push` alone does not carry tags. 4. **Create the GitHub release** against that tag, notes from the CHANGELOG section. -5. **Add or update the entry in [`claude-marketplace`](https://github.com/Digital-Process-Tools/claude-marketplace)** — `/plugin install jit-context@dpt-plugins` resolves through `.claude-plugin/marketplace.json` there, not through this repo. The README documents that install command, so until the marketplace entry exists the first instruction a new user follows fails. +5. **Add or update the entry in [`claude-marketplace`](https://github.com/Digital-Process-Tools/claude-marketplace), and confirm the PR is *merged*, not merely opened, before you count the release done** — `/plugin install jit-context@dpt-plugins` resolves through `.claude-plugin/marketplace.json` there, not through this repo. The README documents that install command, so until the marketplace entry exists the first instruction a new user follows fails. **If the plugin itself was renamed, opening the marketplace PR is not the gate — merging it is** (#457): v0.13.0 through v0.16.0 shipped the `claude-jit-context` → `jit-context` rename while the matching `claude-marketplace` rename PR sat open, so both the README's install command and the `#452` CHANGELOG entry about the `renames` map rewriting `enabledPlugins` were false for the whole gap. Check the live state rather than trusting that a PR exists: `supertool 'repo:Digital-Process-Tools/claude-marketplace' 'gh-pr:N:status'`. `state: OPEN` means the gap is still live and the tag you are about to push repeats #457 — merge the marketplace PR in the same window, or hold the tag. Marketplace entries name the repo, not a version — users get the default branch. A tag is therefore for humans and the changelog, not a pinning mechanism: whatever is on `main` is what installs. diff --git a/changelog.d/457.fixed.release-marketplace-merge-gate.md b/changelog.d/457.fixed.release-marketplace-merge-gate.md new file mode 100644 index 0000000..09e52e4 --- /dev/null +++ b/changelog.d/457.fixed.release-marketplace-merge-gate.md @@ -0,0 +1 @@ +- **The release checklist's marketplace step now requires the `claude-marketplace` PR to be *merged*, not merely opened, before a plugin rename counts as shipped** (#457). v0.13.0 through v0.16.0 shipped the `claude-jit-context` → `jit-context` rename while the matching `claude-marketplace` rename PR sat open, leaving the README's install command and the `#452` entry's claim about the `renames` map false for the whole gap. `.claude/jit-context/paths/00-manual/release.md`'s marketplace step now says to check the live PR state before tagging, rather than trusting that a PR exists.