fix(marketplace): sync marketplace.json version with the plugin manifest - #27
Merged
Merged
Conversation
marketplace.json still advertised 0.2.1 while the plugin manifest had moved to 0.2.2 and now 0.2.3. The marketplace entry is what a client reads to decide whether a newer version is available, so a plugin bump that never reaches it is a release users are never offered.
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
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
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.
.claude-plugin/marketplace.jsonstill advertised0.2.1whileplugins/code-index/.claude-plugin/plugin.jsonhad moved to0.2.2and now0.2.3. Two manifests describing the same plugin disagreed by two releases — the marketplace is what a client reads to decide whether a newer version exists, so a bump that never reaches it is a release users are not offered.Both fields (marketplace
metadata.versionand the plugin entry'sversion) now read0.2.3, matching the plugin manifest that shipsserverVersion0.2.1.Worth a follow-up: nothing enforces that these two files agree, and they have already drifted once silently. A one-line check in CI comparing them would have caught it.