Single file, curated CHANGELOG

[tony]

Hi, thank you for the project!

Feature request
Changelog file

Is your feature request related to a problem? Please describe.
<4.0's changelog was better IMO.

Describe the solution you'd like

• Single file change log
• Curation from maintainer (order by importance)
• More info: keepachangelog.com

Describe alternatives you've considered
There's no alternative but it seems changelog.md was removed in favor of releases in >4.0 in favor of GitHub Releases.

Additional context

See webpack/webpack#15318 for the rationale / example I've given

GitHub Releases (fragmented, undifferentiated, and in a "blog" subsite detached from any changelog file):

152702745-60d062ea-a280-495f-9131-11248c74e82d.mp4

Babel's single file changelog (everything's on one page, at least):

152702755-64967d04-e0fd-4651-b51f-d45ede8fffc8.mp4

Are you willing to (attempt) a PR?

• Yes

  But a maintainer would be a better for this. Also it would be appropriate to curate releases,

[tony]

I should also rewind: I am in a chipper disposition and am happy with the project. Just have a universal distaste for GH Releases.

I've nothing wrong with GH Releases to supplement things, but I'd never suggest it as a replacement for an actual changelog

Example from a project of mine: CHANGES file, CHANGES on docs site, Release

[coolsoftwaretyler]

Hey @tony! Sorry no one got back to you for so long.

I'm going to convert this to a discussion topic, rather than an issue. I don't want to close it out entirely, but I am just sort of getting up to speed on the core team here and I don't have a yes/no for you.

Thanks for the idea, and apologies once more for the delay!

[tony]

@coolsoftwaretyler Thank you!

[tony]

Also - I am still interested in a single file changelog.

I will add a link in the main post to https://keepachangelog.com/en/1.1.0/

[coolsoftwaretyler]

Hey @tony,

I'm gonna close the loop on this. After running a few releases, I've been very happy with the GitHub process. Apologies that it isn't your preferred outcome, but I think we're going to move forward as is for some time.

Thanks for putting it out there, though! Really appreciate your time.

[tony]

It is fine. Thank you for taking the time to maintain the package, and for getting back to this!