bump-version

A release command that updates a project's version number across its code, dependencies, changelog, and release metadata.

In plain words
What is it for?
Use it when publishing a new X.Y.Z release, including updating version references, preparing the changelog, creating a tag, and pushing it.
Why use it?
It reduces the chance of leaving old version numbers in some files or forgetting the associated changelog and Git tag steps.

Command for Claude Code

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/guess/claude_code/bump-version
Clone the repo
git clone --depth 1 https://github.com/guess/claude_code

Made for: Claude Code.

Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 677 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.00006 $0.00677
Opus 5 $0.00003 $0.00338
Sonnet 5 $0.00001 $0.00135
Haiku 4.5 $0.00001 $0.00068

Measured 2d ago against content hash c55caf3e087c, 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 2d 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 · 53 lines

How it starts

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

Update version to the specified X.Y.Z value.

CRITICAL: You MUST Read each file BEFORE attempting to Edit it. The Edit tool will fail if you have not read the file first. Do not skip this step for any file.

Steps

  1. Read mix.exs and get current version.

  2. Search for both version patterns (replace X.Y with actual current major.minor):

    grep -rn "X\.Y" --include="*.md" --include="*.ex" --include="*.exs" . | grep -v deps/ | grep -v _build/ | grep -v CHANGELOG | grep -v '.official/'
    
  3. For each file that needs updating: Read the file first, then Edit it (preserve existing format):

    • Full versions "X.Y.Z" → new full version
    • Dependency specs "~> X.Y" → new major.minor
  4. Read then update CHANGELOG.md:

    • Get the bundled CLI version from @default_cli_version in lib/claude_code/adapter/port/installer.ex
    • Convert Unreleased to [X.Y.Z] - YYYY-MM-DD | CC A.B.C where A.B.C is the CLI version
    • Example: ## [0.18.0] - 2026-02-08 | CC 2.1.37
  5. Verify no old versions remain (except CHANGELOG history)

  6. Tag and release:

    • Create git tag: git tag -a vX.Y.Z -m "vX.Y.Z"
    • Push tag: git push origin vX.Y.Z
    • Extract the release section from CHANGELOG.md (everything between the new version header and the previous version header, excluding the headers themselves)
    • Create GitHub release with CC version in title and changelog as body:
      gh release create vX.Y.Z --title "vX.Y.Z | CC A.B.C" --notes "<changelog section content>"
      

Reference

Files that contain version numbers (6 files + CHANGELOG):

  • mix.exs@version "X.Y.Z"
  • lib/claude_code.ex — version string
  • README.md{:claude_code, "~> X.Y"}
  • docs/guides/custom-tools.md{:claude_code, "~> X.Y"}
  • docs/reference/troubleshooting.md{:claude_code, "~> X.Y"}
  • lib/claude_code/mcp.ex{:claude_code, "~> X.Y"}

Creating retroactive releases (if needed for missed versions):

  1. Find version bump commits: git log --oneline --all --grep='version' -- mix.exs
  2. Create annotated tags: git tag -a vX.Y.Z <commit> -m "vX.Y.Z"
  3. Push all tags: git push origin --tags
  4. Create releases oldest-to-newest, extracting changelog sections as body

Read the full file on GitHub · 53 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. 2d ago First seen · 53 lines · 6 tokens per session scan A c55caf3e087c

Subscribe to this mod's changes

bump-version is a command published in the GitHub repository guess/claude_code (96 stars, last pushed 2mo ago), licensed MIT. It adds 6 tokens to every session and 677 once invoked, about $0.0000 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-30.