version
Stamps the number a plugin releases under. plugin build derives the vendor manifests and never
decides a version; plugin version is the command that writes it, in one call, into plugin.json,
the package’s package.json, the skills’ npx/upx pins, .plugin/pins.json, and marked
mcpServers entries. See the CLI overview for the flags.
The skill’s first question is who decides the number:
| Source | Call | Used by |
|---|---|---|
| Author bump | plugin version minor |
Plain repositories |
| Explicit number | plugin version 1.4.0 |
semantic-release, release-it |
The package’s package.json |
plugin version --from-package |
changesets, release-please with an npm package |
The canonical plugin.json |
plugin version --from-manifest |
release-please with no package.json |
For release-please with no package.json, the skill gives the workflow step that restamps the
release PR, and pushes it with a GitHub App token so the PR’s required checks run. The
CLI overview has it too.
Which release type to use is not the skill’s call. A version is a promise about what broke, so the
skill offers the semver reading and asks. With packagePath declared it does not offer a release type
at all: the package owns the number.
See also
Section titled “See also”- CLI overview for the command, the places it writes, and the release-tool wiring
upgrade-pluginmoves the version your project calls, a different number- ADR-0010