Changelog missing for v4.0.0

[gavinhenderson]

Thanks for all your hard-work on graphql-request, it is much appreciated.

Is there any plans to issue a change log for v4.0.0? Without one I can't be certain what breaking changes it contains, therefore can't confidently upgrade to the latest version.

[arminrosu]

For reference, this is the diff provided by renovate-bot: https://app.renovatebot.com/package-diff?name=graphql-request&from=3.7.0&to=4.0.0

Considering 4.0.0 was released 4 days ago, this should be the git diff: 3.7.0...12c2e8d, ie. PR #303

[jasonkuhrt]

There's problems with the release tool at the moment. The desire to certainly to have change logs. Commit messages are generally well used and should be usable meanwhile.

[lensbart]

Reading the commit messages doesn’t make this immediately clear — are there any breaking changes since 3.7.0?

Thanks

[jasonkuhrt]

This is marked as a breaking change but not sure why, on mobile right now.

12c2e8d

[thegiantbeast]

@jasonkuhrt can you tell me what the breaking change is?

I only see a new feature being added from the commit you shared (cancellation), not changing a previous behaviour, but I could be wrong.

[jasonkuhrt]

I looked again, it seems that official support for Node.js 12 was dropped. Manually noting this in the changelog now:

https://github.com/prisma-labs/graphql-request/releases/tag/4.0.0