chore: drop release-please config; plugin version tracks the CLI#31
Merged
Conversation
The plugin is a distribution of the @elnora-ai/cli skills, and its version is stamped from the CLI on each CLI release — it has no independent version. Remove the unused release-please-config.json and .release-please-manifest.json, and add a "Versioning & releasing" note to the README: the version tracks the CLI, and plugin-only changes ship by merging to main (the marketplace serves the default branch — no tag or publish step). CHANGELOG.md is left as frozen history of the 1.x plugin releases. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
rjamul-elnora-ai
force-pushed
the
chore/version-tracks-cli
branch
from
f7096df to
d9063aa
Compare
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.
Why
This plugin is a distribution of the
@elnora-ai/cliskills, and itsplugin.json/marketplace.jsonversionis stamped from the CLI on each CLI release. So the plugin has no independent version — release-please here only produced a second version number that drifted from the CLI-tracked one. The CLI is the single source of truth (lockstep versioning).Change
release-please-config.jsonand.release-please-manifest.json.main— the marketplace is served from the default branch, so there's no tag or publish step. Hand-bumpplugin.jsononly for a change that affects the installed runtime and must reach existing installs before the next CLI release.CHANGELOG.mdis left as frozen history of the 1.x plugin releases.