v10.2.1
What's Changed
This release introduces semantic version normalization for ASP.NET Core API versioning, ensuring that semantically equivalent version formats (1, 1.0, and 1.0.0) are normalized to identical canonical forms for consistent routing and version matching.
Key improvements:
- RestfulApiVersionReader normalization now treats semantically equivalent API version formats as identical values for routing purposes,
- ApiVersionReader property added to
RestfulApiVersioningOptionsfor advanced version reader customization and extensibility, - Automatic normalization enabled by default when
SemanticApiVersionis the default API version; applications not using semantic versioning retain previous behavior, - Comprehensive test coverage added to verify version normalization across Accept and Content-Type header scenarios, including matching, mismatched, and unregistered version aliases,
- Documentation updated to reflect the version normalization feature, new type documentation for
ApiVersionAliasParser, and configuration guidance forServiceCollectionExtensions.
Note
Version normalization is enabled automatically when using SemanticApiVersion as the default API version. Use RestfulApiVersioningOptions.ApiVersionReader to customize or disable this behavior if needed.
Sources:
- V10.2.1/normalized semanitc versions by @gimlichael in #36
Full Changelog: v10.2.0...v10.2.1