Repository navigation
Add CHANGELOG.md and populate PackageReleaseNotes for upgrade evaluation - #15
Merged
Romain-OD merged 2 commits intoOct 20, 2026
Merged
Conversation
4 tasks
…projects Co-authored-by: Romain-OD <31764259+Romain-OD@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add CHANGELOG.md and populate PackageReleaseNotes for upgrade evaluation
Add CHANGELOG.md and populate PackageReleaseNotes for upgrade evaluation
Oct 14, 2026
Romain-OD
marked this pull request as ready for review
October 20, 2026 16:02
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adopters deciding whether to upgrade from
2.0.0to2.1.0had no changelog and empty<PackageReleaseNotes>on every NuGet.org listing — the place the upgrade decision is actually made. This adds both.Changes
CHANGELOG.md(new, repo root) — Keep a Changelog 1.1.0, backfilled for both shipped releases:2.0.0— flags the middleware-pipeline refactor as Breaking; notes the newNatsNet/AzureEventHubsadapters and thenet8.0+net10.0multi-targeting.2.1.0— the newImmediateValidationsadapter.MessageValidation.RabbitMQcan tell a co-versioned bump does not affect them.[Unreleased]+ compare links; a header comment records the convention to update the changelog before tagging.<PackageReleaseNotes>— one line added to all 10 packable.csproj:Note
Applied per-
.csprojrather than viaDirectory.Build.props. The central-properties change (PR #12) is still unmerged; introducingDirectory.Build.propshere would duplicate and conflict with it. This keeps both PRs independently mergeable — whichever lands second can hoist the line centrally.Verified:
dotnet pack -c Releaseproduces all 10.nupkg, each.nuspeccarrying the<releaseNotes>URL.