CHANGELOG for v2 → v3 → v4 (list of breaking changes)

[kachkaev]

I see a number of warnings from yarn audit because some project dependencies still rely on set-value v2 and v3. While it’s technically possible to force-install v4 via package.json → resolutions, it’s not clear whether that’s a save move or not.

It’d be great if the repo had CHANGELOG.md, UPGRADING.md, MIGRATION.md or info on the Releases page. If major versions are only related to supported Node versions or some rare edge cases, library users can make informed decisions to force-upgrade from v2 or v3.

Examples: jest → CHANGELOG.md & Releases, sentry-javascript → MIGRATION.md & Releases

Related to #38 & #39

[shayc]

Changes between 2.0.1 and 3.x: 2.0.1...3.0.0
Changes between 3.0.0 and 4.0.1: 3.0.0...4.0.1

History up to 3.0: https://github.com/jonschlinkert/set-value/blob/4.1.0/.verb.md#history

TL;DR - Without reading too much into the source code, there has been a NodeJS bump, and maybe some API changes, not sure if they're breaking anything though.