Repository navigation
docs(versioning): a release is not live until the marketplace entry moves - #1
Merged
Merged
Conversation
…oves The catalog pins entries to a release tag, so tagging here ships nothing until version and source.ref move. Added as release step 8. Co-authored-by: Cursor <cursoragent@cursor.com>
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.
Records the marketplace pin as a required release step. Tagging and pushing here ships nothing on its own — the
cadastocatalog pins every entry to a release tag, so users see the old version until that entry'sversionandsource.refmove together.v0.2.0 was tagged and pushed earlier today and is not live for exactly this reason, which is what prompted writing it down.
Changes
docs/versioning.md— adds release step 8 (update the marketplace entry), splits the old "No MCP or marketplace coupling" heading into## No MCP couplingand a new## Marketplacesection with the three-step repin procedure, and corrects the stale claim that the marketplace tracks the default branch with no version pin to bump.AGENTS.md— the marketplace gotcha now says the entry is pinned to a release tag and must be repinned per release, linkingdocs/versioning.md#marketplace.CHANGELOG.md— new[Unreleased]section.Provenance
Authored by @sebastian-iancu as
85279c5ondocs/marketplace-pin-followup, which branched from166c7bfbefore the 0.2.0 release. Rebased onto currentmain(743ad34) and pushed to this branch rather than force-pushing the original, which is untouched at85279c5and can be deleted once this merges.The rebase needed one conflict resolution: the original added its changelog line to
[Unreleased], but that block has since been folded into the released[0.2.0]. Since this change is not in the v0.2.0 tag, it now opens a fresh[Unreleased]section instead.docs/versioning.mdandAGENTS.mdauto-merged, correctly keeping main's markdownlint-free text.Verification
./scripts/validate.shandclaude plugin validate .both pass on the rebased tree.🤖 Generated with Claude Code