Delete the CHANGELOG.md

[jimmywarting]

@node-fetch/core what do you think about ditching the CHANGELOG.md?

Everytime we release a new tag, then we have the possibility to auto generate a changelog from all PR/commits that where added.
that way we don't have to manually keep the changelog up to date.

[jimmywarting]

Here is an example from latest release: https://github.com/node-fetch/node-fetch/releases/tag/v3.1.0

[LinusU]

I'm 👍 on this

This is how I do it in all of my repositories as well

[gr2m]

Once we merge #1270, releases with changelogs will be auto-generated. I'm okay with deleting the CHANGELOG.md file.

[ramya-rao-a]

One catch here is that the generated changelog in the releases does not categorize the changes into breaking changes vs new features vs bug fixes. When there is a major version update, one of the things important for consumers would be to understand what the breaking changes are

[gr2m]

That's not right, semantic-release does separate bug fixes, features, and breaking changes in the release notes it generates.

[ramya-rao-a]

Apologies, I did not see such break up in https://github.com/node-fetch/node-fetch/releases/tag/v3.0.0 and so the comment. I realize now that the v3 release might have been before adapting the auto generated changelog

[gr2m]

we don't use semantic-release yet, #1270 is pending

[github-actions]

🎉 This issue has been resolved in version 4.0.0-beta.1 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This issue has been resolved in version 3.2.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀