dotnet-release-management

Automates .NET release lifecycle with versioning, changelogs, and branching strategies.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/tedtv1007-ctrl/milk-skills-library --skill dotnet-release-management-tedtv1007-ctrl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-release-management
Source: https://github.com/tedtv1007-ctrl/milk-skills-library/tree/main/dotnet-release-management
Command: npx skills add https://github.com/tedtv1007-ctrl/milk-skills-library --skill dotnet-release-management-tedtv1007-ctrl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the complexity of managing .NET project lifecycles, ensuring consistent versioning, automated changelog generation, and reliable release branching strategies.

Core Features & Use Cases

  • Deterministic Versioning: Uses Nerdbank.GitVersioning to calculate unique, commit-based versions automatically.
  • Release Lifecycle Management: Provides standardized workflows for pre-release (alpha/beta/rc) and stable releases using SemVer 2.0.
  • Automated Changelogs: Integrates with git-cliff and conventional commits to maintain accurate, human-readable project history.
  • Use Case: When preparing a new library release, use this skill to automatically bump the version, generate a changelog from recent commits, and create the necessary release branch.

Quick Start

Use the dotnet-release-management skill to initialize NBGV versioning in your current repository.

Frequently Asked Questions about dotnet-release-management

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

FAQPage Schema
How do I automate .NET release versioning and changelog generation?▼

Automate .NET release versioning by using Nerdbank.GitVersioning for commit-based version calculation and git-cliff for changelog generation. This ensures deterministic versioning and standardized release workflows across development, pre-release, and production environments.

What is the best way to manage SemVer 2.0 pre-release workflows for a .NET library?▼

Manage SemVer 2.0 pre-release workflows by applying standardized release lifecycle management. This provides structured branching strategies for alpha, beta, and release candidate stages, ensuring reliable versioning for .NET libraries and applications.

Can I use Nerdbank.GitVersioning to calculate deterministic versions for .NET applications?▼

Yes, you can use Nerdbank.GitVersioning to calculate deterministic versions for .NET applications. It automatically computes unique, commit-based versions to ensure consistent versioning across your development, pre-release, and production lifecycle.

How do I generate a changelog from conventional commits in a .NET project?▼

Generate a changelog from conventional commits by integrating git-cliff into your .NET project workflow. This maintains an accurate, human-readable project history by automatically parsing your git commit messages during the release process.

Does this approach support branching strategies for both .NET libraries and applications?▼

Yes, this release management approach supports branching strategies for both .NET libraries and applications. It standardizes release workflows and manages versioning across development, pre-release, and stable production environments.