V10.2.0/changelog - #35
Conversation
Add API version aliasing support and automatic semantic version alias registration to the 10.2.0 release notes. Documentation updated for both NuGet package consumers and repository contributors.
Greptile SummaryThis PR adds the 10.2.0 changelog and release notes entries for
Confidence Score: 4/5Documentation-only change (changelog and release notes); no executable code is modified, so no functional regression risk. Both files are documentation/release metadata. The only substantive issue is a style inconsistency in the PackageReleaseNotes.txt CHANGED entry — passive voice and a missing trailing phrase ("through custom parsers") relative to the CHANGELOG.md equivalent. .nuget/Codebelt.Extensions.Asp.Versioning/PackageReleaseNotes.txt — the CHANGED documentation entry wording is inconsistent with the rest of the file and diverges from the CHANGELOG.md equivalent. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[10.2.0 Release] --> B[CHANGELOG.md]
A --> C[PackageReleaseNotes.txt]
B --> B1["[10.2.0] - 2026-07-07 section added"]
B --> B2["[Unreleased] link updated to v10.2.0...HEAD"]
B --> B3["[10.2.0] comparison link added"]
C --> C1["# New Features\nADDED ApiVersionAliasParser\nADDED AddApiVersionParser<T>"]
C --> C2["# Improvements\nEXTENDED AddRestfulApiVersioning\nCHANGED Documentation"]
B1 --> F1["Added: ApiVersionAliasParser type"]
B1 --> F2["Added: AddApiVersionParser<T> extension"]
B1 --> F3["Changed: AddRestfulApiVersioning auto-alias"]
B1 --> F4["Changed: Documentation"]
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
A[10.2.0 Release] --> B[CHANGELOG.md]
A --> C[PackageReleaseNotes.txt]
B --> B1["[10.2.0] - 2026-07-07 section added"]
B --> B2["[Unreleased] link updated to v10.2.0...HEAD"]
B --> B3["[10.2.0] comparison link added"]
C --> C1["# New Features\nADDED ApiVersionAliasParser\nADDED AddApiVersionParser<T>"]
C --> C2["# Improvements\nEXTENDED AddRestfulApiVersioning\nCHANGED Documentation"]
B1 --> F1["Added: ApiVersionAliasParser type"]
B1 --> F2["Added: AddApiVersionParser<T> extension"]
B1 --> F3["Changed: AddRestfulApiVersioning auto-alias"]
B1 --> F4["Changed: Documentation"]
Prompt To Fix All With AIFix the following 1 code review issue. Work through them one at a time, proposing concise fixes.
---
### Issue 1 of 1
.nuget/Codebelt.Extensions.Asp.Versioning/PackageReleaseNotes.txt:10
Every other `CHANGED` entry in this file uses the pattern `CHANGED [Subject] [active verb]...` (e.g., "CHANGED Dependencies have been upgraded…", "CHANGED RestfulApiVersioningOptions class … to include…"). The documentation line diverges with passive voice and is also missing the closing phrase "through custom parsers" that appears in the equivalent `CHANGELOG.md` entry at line 22.
```suggestion
- CHANGED Documentation to clarify semantic version alias registration behavior and guidance for exposing additional semantic versions through custom parsers.
```
Reviews (1): Last reviewed commit: "💬 document 10.2.0 release" | Re-trigger Greptile |
|
|
||
| # Improvements | ||
| - EXTENDED AddRestfulApiVersioning to automatically register semantic version aliases when the default API version is a SemanticApiVersion, enabling alias formats such as major, major.minor, and major.minor.patch without explicit configuration, | ||
| - CHANGED Documentation updated to clarify semantic version alias registration behavior and guidance for exposing additional semantic versions. |
There was a problem hiding this comment.
Every other
CHANGED entry in this file uses the pattern CHANGED [Subject] [active verb]... (e.g., "CHANGED Dependencies have been upgraded…", "CHANGED RestfulApiVersioningOptions class … to include…"). The documentation line diverges with passive voice and is also missing the closing phrase "through custom parsers" that appears in the equivalent CHANGELOG.md entry at line 22.
| - CHANGED Documentation updated to clarify semantic version alias registration behavior and guidance for exposing additional semantic versions. | |
| - CHANGED Documentation to clarify semantic version alias registration behavior and guidance for exposing additional semantic versions through custom parsers. |
Prompt To Fix With AI
This is a comment left during a code review.
Path: .nuget/Codebelt.Extensions.Asp.Versioning/PackageReleaseNotes.txt
Line: 10
Comment:
Every other `CHANGED` entry in this file uses the pattern `CHANGED [Subject] [active verb]...` (e.g., "CHANGED Dependencies have been upgraded…", "CHANGED RestfulApiVersioningOptions class … to include…"). The documentation line diverges with passive voice and is also missing the closing phrase "through custom parsers" that appears in the equivalent `CHANGELOG.md` entry at line 22.
```suggestion
- CHANGED Documentation to clarify semantic version alias registration behavior and guidance for exposing additional semantic versions through custom parsers.
```
How can I resolve this? If you propose a fix, please make it concise.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
This pull request introduces API version aliasing support and improves semantic version alias registration in the
Codebelt.Extensions.Asp.Versioningpackage. The main changes include a new parser for friendly API version aliases, an extension method for custom parser registration, and enhancements to automatic alias registration for semantic versions. Documentation has also been updated for clarity.New Features:
ApiVersionAliasParserto resolve friendly API version aliases (e.g.,1,1.0,1.0.0) before delegating to another parser, enabling callers to use shortened or compatibility-oriented tokens. [1] [2]AddApiVersionParser<T>extension method for registering customIApiVersionParserimplementations as the singleton parser for API versioning services. [1] [2]Improvements:
AddRestfulApiVersioningto automatically register semantic version aliases when the default API version is aSemanticApiVersion, reducing the need for explicit configuration. [1] [2]Documentation:
Release Management:
10.2.0.Add API version aliasing support and automatic semantic version alias registration to the 10.2.0 release notes. Documentation updated for both NuGet package consumers and repository contributors.