Please consider updating the CHANGELOG

[runephilosof-abtion]

The Github release notes are not part of the version history and they are not user friendly.

If you include the CHANGELOG.md in git, you can review what is included there, in the PR making the related change.

As an example of the user unfriendliness, try finding the release notes for v2.12 (not only that specific version, but those around that time to get an overview).
https://github.com/lostisland/faraday/releases?q=v2.12&expanded=true Shows v2.14 versions.

CHANGELOG.md gives a good overview of the versions and timeline.
You can search through a file with normal tools.
It is easy to find versions that introduce changes that you are interested in.
Having version history for the changelog in itself is a benefit.

[runephilosof-abtion]

I am also interested in hearing why it was chosen to move to Github release notes.
I assume you have a tool that makes it easier to manage than the CHANGELOG file?

[olleolleolle]

@runephilosof-abtion yeah, there's a button "auto-include relevant commit comments", which makes it a routine-click action to make a release with release notes. In addition, the Release button not only creates that GitHub Release, it also triggers a GitHub Actions workflow that ends up publishing the RubyGem.