Repository navigation
Conversation
) 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 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
v0.13.0 through v0.16.0 shipped the
claude-jit-context->jit-contextrename while the matchingclaude-marketplacerename PR (#5 there) sat open. Confirmed still live today (2026-10-06):supertool 'repo:Digital-Process-Tools/claude-marketplace' 'gh-pr:5:status'reports that PR as OPEN, mergeable, not merged. Its diff adds therenames: {"claude-jit-context": "jit-context"}map and renames the marketplace entry itself tojit-contextwithref: release-- so with it unmerged, the marketplace has no entry namedjit-contextat all, and/plugin install jit-context@dpt-pluginscurrently fails outright even for a brand-new install, not only for rename resolution on an existing one.Both the README's documented install command and the
#452CHANGELOG entry's claim that "the marketplace's renames entry rewrites your enabledPlugins key by itself" were false for the whole v0.13.0-v0.16.0 gap, because nothing in the release checklist required the marketplace PR to be merged before counting a rename shipped -- only that an entry existed or was opened.This PR hardens
.claude/jit-context/paths/00-manual/release.md's marketplace checklist step (step 4 onmain) so that, for a plugin rename, opening the marketplace PR is explicitly named as not the gate -- merging it is. The step now names #457 as precedent and gives the live check command to run before tagging.What this PR does not do, and could not do from here: it does not merge
claude-marketplacePR #5 (Digital-Process-Tools/claude-marketplace#5). That is a different repository's maintainer-write-access decision, explicitly out of scope for this run (the issue itself says the release that filed it was told not to touchclaude-marketplaceorclaude-oss). The two release-notes claims #457 names (README.md's install line, the historical #452 CHANGELOG entry) remain false on disk until that PR merges -- this PR only prevents the same gap from being repeated silently on a future rename, by making the checklist check the merge state rather than trust that a PR exists.README.md and CHANGELOG.md were deliberately left unchanged: CHANGELOG's #452 entry is historical (inside the already-released
## [0.13.0]section) and this repo's convention is never to hand-edit it retroactively; README's install command is the correct long-term instruction once PR #5 merges, so caveating it now would just be reverted later without addressing where the actual defect lives (the cross-repo merge timing).Outstanding cross-repo action for a maintainer with write access to
Digital-Process-Tools/claude-marketplace: merge PR #5 (Digital-Process-Tools/claude-marketplace#5). This PR does not and cannot do that.Part of #457 -- stays open until claude-marketplace#5 merges (a different repository's maintainer action this PR cannot perform); this PR only hardens the checklist so the gap is not repeated on a future rename.
🤖 Generated with Claude Code
[AI-generated]