versioning

Configure API versioning for .NET projects with URL, header, and query methods.

4|1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/FaysilAlshareef/dotnet-ai-kit --skill versioning-faysilalshareef
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: versioning
Source: https://github.com/FaysilAlshareef/dotnet-ai-kit/tree/main/skills/api/versioning
Command: npx skills add https://github.com/FaysilAlshareef/dotnet-ai-kit --skill versioning-faysilalshareef

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and implement robust API versioning strategies in .NET projects to prevent breaking changes for clients and to manage the lifecycle of multiple API versions.

Core Features & Use Cases

  • Versioning patterns including URL segment, header-based, and query-string approaches to accommodate different client needs.
  • Support for both Controllers and Minimal APIs with per-version routing and versioned OpenAPI documents.
  • Sunset policies and deprecation workflows to guide client migrations and communicate timelines clearly.
  • Discovery and validation tooling to detect existing versioning usage and ensure consistent versioning across services.

Quick Start

Configure API versioning in Program.cs using AddApiVersioning, define the default version, and apply versioned routes for new endpoints.

Frequently Asked Questions about versioning

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

FAQPage Schema
How do I configure API versioning in .NET Minimal APIs?

Configure API versioning in .NET Minimal APIs by using AddApiVersioning in Program.cs to define a default version, then apply versioned routes to new endpoints to manage multiple API versions safely.

What's the best way to implement a sunset policy for deprecated .NET API versions?

The best way to implement a sunset policy for deprecated .NET API versions is to apply deprecation workflows that guide client migrations and communicate timelines clearly through per-version OpenAPI documents.

Can I use header-based and query-string API versioning patterns in the same .NET project?

Yes, you can apply URL segment, header-based, and query-string API versioning patterns in the same .NET project to accommodate different client needs and manage version discovery across services.

How do I generate per-version OpenAPI docs for multiple .NET API versions?

Generate per-version OpenAPI docs for multiple .NET API versions by configuring versioned routing for Controllers and Minimal APIs, ensuring consistent document generation for each defined API version.

Why do I need to validate existing API versioning usage before adding a new version?

Validating existing API versioning usage ensures consistent versioning across services, detects current patterns, and enforces discovery and routing best practices to prevent breaking changes for clients.