bump-plugin-version

Featured

(project) Use when editing any file under skills/ or plugins/ to bump the plugin version before committing

DevOps & Infrastructure 129 stars 25 forks Updated today MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
70
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
47
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Bump Plugin Version After editing files under `skills/` or `plugins/`, bump the plugin's `version` field in `.claude-plugin/marketplace.json` (the repo-root marketplace manifest). It is the single source of versions: each plugin is an entry in its `plugins` array, and there are no per-plugin `plugin.json` files. - **Patch** (0.2.0 -> 0.2.1): bug fixes, config changes, style cleanup - **Minor** (0.2.0 -> 0.3.0): new features, new hooks, new commands - **Major** (0.2.0 -> 1.0.0): breaking changes to hook behavior or config format ## Before bumping Compare the working-tree version against the version on `origin/main`: ```bash git show origin/main:.claude-plugin/marketplace.json ``` If the plugin's version already differs from `origin/main`, it was already bumped for unreleased work. **Do not bump again.** Only bump when the working-tree version matches `origin/main`. If both plugins changed, check each independently.

Details

Author
vinta
Repository
vinta/hal-9000
Created
10 years ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category