docs: document plugin version bump rules#25
Open
Lotte-Verheyden wants to merge 1 commit intomainfrom
Open
Conversation
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.
Summary
Adds a "Plugin Version Bumps" section to
agents.mdso contributors (human or agent) know when to bump theversionfield in the two plugin manifests.The repo ships to two marketplaces with separate manifests (
.claude-plugin/plugin.jsonand.cursor-plugin/plugin.json) that must stay in lockstep. Considered automation (release-please, manualworkflow_dispatchmodeled on the langfuse SDK repos) but settled on a lightweight docs-only approach: contributors bump the version in the same PR as the change, using semver judgment described inagents.md.The new section covers: