bump-version

Automate Semantic Versioning assessment and PR-based SDK version bumps via gh CLI.

4.5k|777|Updated Mar 10, 2025
One-click install
npx skills add https://github.com/modelcontextprotocol/csharp-sdk --skill bump-version-modelcontextprotocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bump-version
Source: https://github.com/modelcontextprotocol/csharp-sdk/tree/main/.github/skills/bump-version
Command: npx skills add https://github.com/modelcontextprotocol/csharp-sdk --skill bump-version-modelcontextprotocol

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Automates assessing and updating the SDK's version number based on Semantic Versioning guidelines, ensuring consistent release management.

Core Features & Use Cases

  • Version assessment: Reads current SDK version, evaluates queued changes, and determines the appropriate next version.
  • Automated branch creation: Generates a new branch with updated version info in Directory.Build.props.
  • Pull request management: Creates PRs with proper labels and descriptive titles to streamline release workflows.
  • Use Case: When preparing a release, automatically determine if the version should bump minor or major, update project files, and open a PR for review.

Quick Start

Use the bump-version skill to analyze recent changes and prepare the version bump by creating a pull request.

Frequently Asked Questions about bump-version

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

FAQPage Schema
How do I automate SDK version bumping based on Semantic Versioning rules?

To automate SDK version bumping based on Semantic Versioning, this skill assesses recent changes and applies the correct version update to project files. It evaluates queued modifications to determine whether a minor or major version increment is required.

Do I need the gh CLI to automate version updates and pull request creation?

Yes, you need the gh CLI installed and authenticated to automate version updates and pull request creation. The skill relies on the GitHub CLI to manage pull requests, apply proper labels, and access repository metadata during the release workflow.

What is the best way to assess queued changes for a SemVer release?

The best way to assess queued changes for a SemVer release is to analyze recent repository modifications against current version info. This skill reads the existing version from Directory.Build.props and determines the appropriate next version automatically.

How does automated version bumping update project files like Directory.Build.props?

Automated version bumping updates project files by creating a new branch and modifying Directory.Build.props with the calculated version number. It ensures consistent release management by applying the Semantic Versioning update directly to your project configuration.

Can I use this automated version assessment for any GitHub release workflow?

You can use this automated version assessment for GitHub release workflows requiring consistent and safe version updates. It streamlines the process by generating a descriptive pull request for review after determining the appropriate version increment.

Why should I automate pull request creation for version updates?

Automating pull request creation for version updates streamlines release workflows by ensuring proper labels and descriptive titles are applied consistently. It removes manual error from SDK release management and centralizes the version bump review process.