list of breaking changes v7

[mesqueeb]

I see that latest version is 7 on npm but the CHANGELOG file here only goes until 6.
How can we upgrade to v7?

[coler-j]

Yes, for example what is valueResult and what is it for?

Used https://docs.github.com/en/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits#comparing-commits to check DIFF

[mesqueeb]

@chris-pardy
would be great if you could also update the Github Releases, just for posterity's sake : )

[marc-at-brightnight]

would suggest using semantic-release, so you don't manually need to manage changelog, versioning and publish.

[ashishtilara]

Also it seems tags are out of sync as well.

[Matthew-Smith]

I'm very hesitant to upgrade to anything v7 without knowing what breaking changes were introduced over v6

[robross0606]

Agreed, the release information is all behind. Neither the CHANGELOG.md nor the Releases section of GitHub is updated. Nor are they even in sync with each other. GitHub says the latest release is 6.5.0. The CHANGELOG.md says the latest release is 6.1.0. Neither is correct.

[freitasskeeled]

👋🏼 any update? Upgrade to v7 blocked by the lack of release notes or changelog

[robross0606]

I'm really surprised this is being completely ignored by repo maintainers. How can anyone be expected to upgrade a major version when there's zero documentation on what was broken or how to migrate?