version

name

version

description

Use this skill to move a universal agent plugin's version — bump it, set an explicit one, cut a release number, or reconcile a version that drifted between the canonical plugin.json and its npm package.json. Handles both release models: a changesets repository, where the number is decided by the release and carried in with publish sync-version, and a plain repository, where plugin version does the whole move. Trigger on "bump the plugin version", "release a new version of this plugin", "set the plugin version to 1.0.0", "cut a patch release", or "the manifest and package.json versions disagree".

Move a plugin's version

Bump or set the version a plugin releases under, keeping every file that carries one in sync.

A plugin's version lives in up to five places, but only two are authored — the canonical root plugin.json and, when the project declares a packagePath, that package.json. The per-vendor manifests, the local marketplace catalogs, and the npx/upx pins inside skills/**/SKILL.md are all derived. So never hand-edit a version: editing one file leaves the other authored file and every derived artifact stale, and a consumer's plugin cache is keyed by version, so a content change without a matching bump is invisible to them.

Step 0 — Does this repo use changesets?

test -d .changeset && echo "changesets"

If it does, the version number is decided by changesets, not by you. Add a changeset and let the release run — the repo's version script should already call publish sync-version, which carries the released number from package.json into the canonical manifest:

npx universal-plugin publish sync-version