Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This release bump updates
VersionPrefix, but the shared package-validation baseline in the same file is still1.0.0(dotnet/nuget-package.props:16-19). That contradicts both the local invariant that the baseline "should be the latest version available on NuGet" and the documented release step inCONTRIBUTING.md:100-105. Since released packages import this file and setIsReleased=true(for exampledotnet/src/Microsoft.Agents.AI/Microsoft.Agents.AI.csproj:4,18), leaving the stale baseline means GA validation will continue comparing against the initial release instead of the current public package line.