Publish changelogs for patch versions

[oronf-mda]

I can't find a changelog for version 10.0.1 of Asp.Versioning.Http, Asp.Versioning.Mvc and Asp.Versioning.OData, and version 10.0.2 of Asp.Versioning.OData

Please publish a GitHub release whenever a new version is published.

[commonsensesoftware]

I don't publish releases for patches. I never have and I don't plan to start. It's often too noisy. The change log for patches are included in the Release Notes section of the README.md for each package/library. Asp.Versioning.Http published its release notes.

When there are no release notes, then a link is tracked back to point to the corresponding GitHub release, which will contain the overall change log. The only real exception to that is if the patch version bumps due to a transitive dependency since the last release, but with no changes. It doesn't happen all that often, but that's just what happened with Asp.Versioning.Mvc and Asp.Versioning.OData. Asp.Versioning.Abstractions bumped a minor version because a single, new visible type, but there are no functional or visible changes down stream. In all other cases, I usually just add a single item that says something to the effective of "Version bump".

When I do publish a release, I collate the change from the previous release to the current release, which includes all patches. A release for every patch is much for one-man show. As the project has gotten larger with more features and libraries, that has made it even more work. Alternatively, I could slow down releases so they are more controlled so that a release can always be paired, but when an issue does arise, I try to get a fix out as quick as possible.

I chose to do this way so that the last release link stays constant and patch release notes are still there. The <PackageReleaseNotes> does allow plain text to be converted to markdown. It comes down to a difference between how legible things are when you open a NuGet package (say the local NuGet Package Explorer) versus viewing it on www.nuget.org. Viewing it on the site looks better in the Release Notes section, which this can be too dense or long when opened in the local package explorer. IIRC, there also did not used to be a Release Notes section on the web site, which is why I ended up merging the release notes into the README.md to be begin with. It's been this way for 5+ years so the original motivation is a little hazy. Since there is an official Release Notes section on the website now, I could be convinced to change where the patch release notes go to make discoverability easier.

A new minor release is coming soon and it will have an official release with the full change log.

[commonsensesoftware]

I was convinced. I updated the build process put release notes in the Release Notes section instead of appending to the README.md. It actually makes the build so much simpler. If there are no release notes, it will still fallback to the last release link on GitHub. This seems to all be the happy compromise. The release notes were there, but just not where one might expect. IIRC, there was a historical reason for this from years ago that may have been fixed or updated.

10.2.0 will be the first release that has this behavior. You don't see individual release notes until the next patch though. GitHub releases will continue to be the stamped and collated set of notes.

I hope that is more inline with what you were hoping for.