Slash Command

/cpv-bump-version

Bump plugin version + run the full publish pipeline (plugin.json, pyproject.toml, README badge, CHANGELOG, push, release)

npx claudepluginhub emasoft/emasoft-plugins --plugin claude-plugins-validation

Prompt Preview

Bump version AND run the full publish pipeline (TRDD-bbff5bc5 — single
entry point):



`publish.py` is the canonical entry point — it bumps the version in
plugin.json + pyproject.toml + `__version__` vars, refreshes the README
badge, regenerates the CHANGELOG, refreshes `.plugin-self-hashes.json`
(if present), commits + tags + pushes, then creates the GitHub release.
Every gate must pass before any push (no `--skip-*` flags exist).

For version-only bumps without push (rare — e.g. CI smoke tests):



`bump_version.py` is now a thin wrapper around `publish.bump_semver` and
exists only for c...

Command Content

Stats

Stars3

Forks0

Last CommitMay 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Bump version AND run the full publish pipeline (TRDD-bbff5bc5 — single entry point): `publish.py` is the canonical entry point — it bumps the version in plugin.json + pyproject.toml + `__version__` vars, refreshes the README badge, regenerates the CHANGELOG, refreshes `.plugin-self-hashes.json` (if present), commits + tags + pushes, then creates the GitHub release. Every gate must pass before any push (no `--skip-*` flags exist). For version-only bumps without push (rare — e.g. CI smoke tests): `bump_version.py` is now a thin wrapper around `publish.bump_semver` and exists only for c...

uv run "${CLAUDE_PLUGIN_ROOT}/scripts/publish.py" --patch # 1.2.0 -> 1.2.1 uv run "${CLAUDE_PLUGIN_ROOT}/scripts/publish.py" --minor # 1.2.0 -> 1.3.0 uv run "${CLAUDE_PLUGIN_ROOT}/scripts/publish.py" --major # 1.2.0 -> 2.0.0 uv run "${CLAUDE_PLUGIN_ROOT}/scripts/publish.py" --dry-run --patch # preview only

Bump version AND run the full publish pipeline (TRDD-bbff5bc5 — single entry point):

uv run "${CLAUDE_PLUGIN_ROOT}/scripts/publish.py" --patch   # 1.2.0 -> 1.2.1
uv run "${CLAUDE_PLUGIN_ROOT}/scripts/publish.py" --minor   # 1.2.0 -> 1.3.0
uv run "${CLAUDE_PLUGIN_ROOT}/scripts/publish.py" --major   # 1.2.0 -> 2.0.0
uv run "${CLAUDE_PLUGIN_ROOT}/scripts/publish.py" --dry-run --patch  # preview only

publish.py is the canonical entry point — it bumps the version in plugin.json + pyproject.toml + __version__ vars, refreshes the README badge, regenerates the CHANGELOG, refreshes .plugin-self-hashes.json (if present), commits + tags + pushes, then creates the GitHub release. Every gate must pass before any push (no --skip-* flags exist).

For version-only bumps without push (rare — e.g. CI smoke tests):

uv run "${CLAUDE_PLUGIN_ROOT}/scripts/bump_version.py" --patch   # local-only

bump_version.py is now a thin wrapper around publish.bump_semver and exists only for callers that need the version number without triggering the full pipeline. New code should call publish.py directly.

See the plugin-management skill for version bump details.