LlmSemverBump 1.1.0

semver-bump

AI-powered semantic versioning for .NET NuGet packages. Analyzes your git history using Claude to determine the correct semver bump.

How It Works

1. Finds the latest git tag as the baseline version
2. Gathers all commits and code diffs since that tag
3. Sends the changes to Claude, which analyzes the public API surface
4. Returns major, minor, or patch with reasoning

Claude examines the actual code — not just commit messages — so it catches things like removed public methods, new interfaces, renamed properties, and other API surface changes that conventional-commits-based tools would miss.

Installation

# As a global tool
dotnet tool install -g LlmSemverBump

# As a local tool (per-repo)
dotnet new tool-manifest  # if you don't have one yet
dotnet tool install LlmSemverBump

Prerequisites

• .NET 8.0 SDK or later
• Git
• Claude Code CLI installed and authenticated

Authenticating Claude Code

llm-semver-bump invokes the claude CLI under the hood, so Claude Code must be authenticated before use. There are two ways:

Interactive login (local development):

claude login

API key (CI/headless environments): set the ANTHROPIC_API_KEY environment variable and Claude Code will use it automatically:

export ANTHROPIC_API_KEY=sk-ant-...

Usage

Dry Run (default)

# Analyze the current repo
llm-semver-bump

# Analyze a specific repo
llm-semver-bump --repo /path/to/repo

Output goes to stderr (reasoning, context) and stdout (just the version), so you can easily capture the version in scripts:

NEW_VERSION=$(llm-semver-bump)

Apply Changes

# Update all .csproj files and create a git tag
llm-semver-bump --apply --git-tag

# Update a specific .csproj only
llm-semver-bump --apply --csproj src/MyLib/MyLib.csproj

Output Formats

# JSON (for CI integration)
llm-semver-bump --output json

# Version only (no reasoning on stderr)
llm-semver-bump --output version-only

# Default text (reasoning on stderr, version on stdout)
llm-semver-bump --output text

Options

GitHub Actions Example

name: Version Bump on Push to Main

on:
  push:
    branches: [main]

jobs:
  version:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0  # Full history needed for git describe

      - uses: actions/setup-dotnet@v4
        with:
          dotnet-version: '8.0.x'

      - name: Install semver-bump
        run: dotnet tool install -g SemverBump

      - name: Bump version
        env:
          ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}  # authenticates Claude Code CLI
        run: |
          llm-semver-bump --apply --git-tag
          git push --tags
          git push

      - name: Pack & publish
        run: |
          dotnet pack -c Release
          dotnet nuget push **/*.nupkg --source nuget.org --api-key ${{ secrets.NUGET_KEY }}

How Claude Decides

The prompt instructs Claude to follow standard semver rules for .NET libraries:

• MAJOR: Removed/renamed public types or members, changed method signatures, interface member additions (breaks implementors), namespace restructuring
• MINOR: New public types/methods/properties, new optional parameters with defaults, new enum values, backwards-compatible features
• PATCH: Bug fixes, internal refactoring, docs, tests, dependency updates, performance improvements

Claude sees both the commit messages and the actual code diff, focusing on the public API surface (classes, interfaces, methods, properties with public/protected visibility). For very large diffs, the tool automatically summarizes to only public API changes to stay within token limits.

Tips

• Use Sonnet for cost efficiency: The default model (claude-sonnet-4-6) balances quality and cost well. Use --model claude-opus-4-6 for complex repos.
• Dry run in CI: Run without --apply first and inspect the JSON output before committing to automated bumps.

License

MIT