Stats
Actions
Tags
From claude-plugins-validation
Bump plugin version and run the full publish pipeline (plugin.json, pyproject.toml, README badge, CHANGELOG, push, release). Use when bumping version + publishing the current plugin via publish.py. Used dynamically via the-skills-menu (TRDD-478d9687).
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-plugins-validation:bump-versionWhen to use
When the cpv-main-menu user picks Manage → Bump version, or any flow needs to bump version + publish the current plugin via publish.py
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Bumps the plugin version AND runs 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 m...
Bumps the plugin version AND runs 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). Loaded by cpv-main-menu-agent via the Manage → Bump version menu branch.
uv on PATHgh CLI authenticated for GitHub release creationPLUGIN_SKIP_GITHUB_INTEGRITY=1 NOT set unless intentionally skipping integrity gategit status).--patch, --minor, or --major.--dry-run to confirm the new version, CHANGELOG entry, and gate-pass list.publish.py enforces every quality gate before push.publish.py is idempotent (interrupted runs resume cleanly).Copy this checklist and track your progress:
--dry-run reviewedpublish.py invocation executedplugin.json::version, pyproject.toml::version, __version__ varsCHANGELOG.md entry| Error | Resolution |
|---|---|
| Gate failure (lint/test/validate) | Fix the underlying issue, re-run (publish.py resumes idempotently) |
| Dirty working tree | git stash or commit changes before bumping |
gh auth not set up | Run gh auth login first |
| Network timeout on push | Re-run; publish.py picks up where it left off |
| Version conflict on push | Pull first, resolve, re-run |
# Patch bump (1.2.0 -> 1.2.1)
uv run "${CLAUDE_PLUGIN_ROOT}/scripts/publish.py" --patch
# Minor bump (1.2.0 -> 1.3.0)
uv run "${CLAUDE_PLUGIN_ROOT}/scripts/publish.py" --minor
# Major bump (1.2.0 -> 2.0.0)
uv run "${CLAUDE_PLUGIN_ROOT}/scripts/publish.py" --major
# Preview only
uv run "${CLAUDE_PLUGIN_ROOT}/scripts/publish.py" --dry-run --patch
For version-only bumps without push (rare — e.g. CI smoke tests):
uv run "${CLAUDE_PLUGIN_ROOT}/scripts/bump_version.py" --patch
bump_version.py is 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.
plugin-management skill — version bump detailscanonical-pipeline skill — publish.py pipeline standardspublish-to-marketplace skill — marketplace notification after publishnpx claudepluginhub emasoft/emasoft-plugins --plugin claude-plugins-validationProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.