bump-version

A release command that updates a plugin's version and prepares its release. A changelog is a record of changes included in each release, while a tag is a named marker in Git for a particular version.

In plain words
What is it for?
Use it for patch, minor, major, or custom version releases, generating changelog entries from commits, committing and tagging the result, pushing it, and syncing the marketplace repository.
Why use it?
It removes repetitive release work and keeps version files, release notes, Git history, tags, pushed changes, and the marketplace repository synchronized.

Command for Claude Code

Part of the claude-workflow plugin — 10 skills, 25 commands, 3 agents, 6 hooks shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/parkerm2/create-claude-workflow/bump-version
Clone the repo
git clone --depth 1 https://github.com/ParkerM2/create-claude-workflow

Made for: Claude Code.

Or install claude-workflow, the plugin that ships this one along with the rest of its 10 skills, 25 commands, 3 agents, 6 hooks.

Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,241 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00019 $0.01241
Opus 5 $0.00010 $0.00620
Sonnet 5 $0.00004 $0.00248
Haiku 4.5 $0.00002 $0.00124

Measured 3d ago against content hash 59f3d7067459, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

bump-version scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/bump-version.md · 130 lines

How it starts

The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/bump-version — Automated Release

Automates the full release process from RELEASING.md. Bumps version across all files, writes changelog, commits, tags, pushes, and updates the marketplace repo.

Phase 1: Determine Version

  1. Read the current version from .claude-plugin/plugin.json (the "version" field).
  2. Ask the user which bump type to apply:
    • Patch (X.Y.Z → X.Y.Z+1) — bug fixes, minor tweaks
    • Minor (X.Y.Z → X.Y+1.0) — new features, non-breaking changes
    • Major (X.Y.Z → X+1.0.0) — breaking changes
    • Custom — user specifies exact version string
  3. Compute the new version string.

Phase 2: Generate Changelog Entry

  1. Run git log to find all commits since the last version tag:
    # Find the latest version tag
    LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
    
    # Get commits since that tag (or all commits if no tag)
    if [ -n "$LAST_TAG" ]; then
      git log "${LAST_TAG}..HEAD" --oneline --no-merges
    else
      git log --oneline --no-merges -20
    fi
    
  2. Categorize commits into Added, Changed, Fixed, Removed sections based on commit message prefixes:
    • feat: / add: → Added
    • fix: → Fixed
    • refactor: / chore: / perf: → Changed
    • remove: / delete: → Removed
    • Other → Changed
  3. Draft a changelog entry using today's date and present it to the user for review.
  4. User approves or edits the changelog entry.

Phase 3: Apply Version Bump

Update the version in these files (all must match):

  1. .claude-plugin/plugin.json — update the "version" field
  2. CHANGELOG.md — prepend the new entry at the top (below the # Changelog header, above the previous version entry). Include the ### Update block:
    ### Update
    
    /plugin update claude-workflow@claude-workflow-marketplace
  3. marketplace/.claude-plugin/marketplace.json — update BOTH metadata.version AND plugins[0].version

Phase 4: Commit, Tag, and Push Plugin Repo

Read the full file on GitHub · 130 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 130 lines · 19 tokens per session scan A 59f3d7067459

Subscribe to this mod's changes

bump-version is a command published in the GitHub repository ParkerM2/create-claude-workflow (4 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 1,241 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.