bump-nuget-version

Increment NuGet package versions and create release branches across Gum projects.

597|79|Updated Mar 11, 2015
One-click install
npx skills add https://github.com/vchelaru/Gum --skill bump-nuget-version
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bump-nuget-version
Source: https://github.com/vchelaru/Gum/tree/main/.claude/skills/bump-nuget-version
Command: npx skills add https://github.com/vchelaru/Gum --skill bump-nuget-version

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing and updating NuGet package versions manually across multiple projects can be error-prone and time-consuming. This Skill automates the version bumping process to ensure consistent, chronological versioning and streamlined release preparation.

Core Features & Use Cases

  • Version Detection: Queries NuGet to find the latest published version for the current day and computes the next incremental version automatically.
  • Multi-Project Update: Updates the <Version> tag in all related project files simultaneously to maintain consistency.
  • Branch Management: Automatically creates and pushes a release branch named after the new version, ready for triggering deployment workflows.

Quick Start

Use the bump-nuget-version skill to automatically increment today’s NuGet package versions across all Gum projects and create the corresponding release branch.

Frequently Asked Questions about bump-nuget-version

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

FAQPage Schema
How do I automate NuGet package versioning across multiple C# projects?

To automate NuGet package versioning across multiple C# projects, this skill queries the latest published versions and increments them based on today's date. It then updates the <Version> tags across all related project files simultaneously to maintain consistency.

What's the best way to create and push release branches for NuGet package updates?

The best way to create release branches for NuGet updates is to use an automated branching workflow. This skill automatically creates and pushes a release branch named after the newly computed version number to support automated release workflows.

How does date-based version incrementing work for NuGet packages?

Date-based version incrementing works by querying NuGet for the latest published version for the current day. The system computes the next incremental version chronologically, ensuring consistent version tagging without manual calculation.

Can I use this automated version bumping for both libraries and CLI tools?

Yes, you can use this automated version bumping for both libraries and CLI tools. The skill is specifically designed to manage version updates and release branch creation across multiple project types, including libraries and command-line interface tools.

How do I ensure consistent version tagging when releasing multiple NuGet packages at once?

To ensure consistent version tagging when releasing multiple NuGet packages, this skill updates the <Version> tag in all related project files simultaneously. This prevents version mismatch errors that occur during manual multi-project updates.