Description
Is your feature request related to a problem? Please describe.
Our releases are mostly automated now publishing to GitHub Releases, including splatting a summary of the the changes since last release into the notes, e.g. https://github.com/pantsbuild/pants/releases/tag/release_2.18.0rc5.
For a stable release, this typically ends up with... nothing useful, e.g. https://github.com/pantsbuild/pants/releases/tag/release_2.17.1
In theory a user could click through all the dev, alpha and rc releases to see the changes, but... it's very annoying. For instance a search like https://github.com/pantsbuild/pants/releases?q=release_2.18&expanded=false (or similar) seems to find all releases, not just ones in the 2.18 series 😦
Describe the solution you'd like
A stable release should include all changes since the last relevant stable release (e.g. 2.17.1 would show 2.17.0 to 2.17.1, 2.18.0 would show 2.17.0 to 2.18.0).
For the 2.x.0 releases, we can continue manually pasting the manually curated "what's new" summary at the start, but that summary can potentially be less extensive if we have all the individual PRs included.
Describe alternatives you've considered
None
Additional context
- https://pantsbuild.slack.com/archives/C046T6T9U/p1699891418833649
- Changelog entries #20172 will make the auto-changelog easier to interpret/more useful.
Activity