version-bump

Bumps the ai-raccoon tool version via a script and verifies the packed NuGet artifact.

2|Updated Aug 2, 2026
One-click install
npx skills add https://github.com/Arasz/ai-raccoon --skill version-bump-arasz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-bump
Source: https://github.com/Arasz/ai-raccoon/tree/main/.ai-badger/skills/learned/software-development/version-bump
Command: npx skills add https://github.com/Arasz/ai-raccoon --skill version-bump-arasz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Manually updating version numbers across a .NET project risks inconsistent markers between the VERSION file, build props, and the packed MCP server manifest. This Skill automates the semver bump and proves the packed NuGet artifact carries the correct version. ## Core Features & Use Cases - Scripted Semver Bump: Run scripts/version-bump.py with patch, minor, or major to update the single hand-written VERSION file at the repo root. - Derived Version Chain: Directory.Build.props reads VERSION so assembly versions follow automatically, and a csproj target substitutes the version into the generated .mcp/server.json at pack time. - Contract Test Gate: VersionContractTests run dotnet pack and open the resulting .nupkg to verify the packed server.json carries the VERSION value. - Use Case: After merging a user-facing feature, run a minor bump, execute the VersionContractTests filter, and add a compact README "What's new" entry before shipping. ## Quick Start Bump the ai-raccoon version by one minor level and run the version contract tests to confirm the packed artifact is correct.

Frequently Asked Questions about version-bump

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bump the version of a .NET tool with a script?

Run python3 scripts/version-bump.py with patch, minor, or major. The script updates the VERSION file at the repo root, which is the only hand-written version marker, and fails loudly if it does not find exactly one occurrence of the current version.

When should I choose patch vs minor vs major version bump?

Use patch for bug fixes and internal refactors, minor for a user-facing feature, and major for a breaking change. For example, 1.8.0 becomes 1.8.1, 1.9.0, or 2.0.0 respectively.

How does the version reach the packed NuGet package?

Directory.Build.props reads the VERSION file to set $(Version), and a csproj target substitutes it into a generated copy of .mcp/server.json during packing. The tracked server.json only contains the literal token __VERSION__, never a real semver.

How do I verify the packed .nupkg has the correct version?

Run dotnet test on the AiRaccoon.Tests project filtered to VersionContractTests. The PackedMcpServerJson_CarriesTheVersionFileVersion test runs dotnet pack itself and reads .mcp/server.json out of the resulting .nupkg zip.

When should the README What's new section be updated?

Add a compact entry only for a braggable user-facing feature, with no prose and no internal fixes. The root README is packed as the NuGet package readme, so the entry also appears on nuget.org.