fix: drop support for Node 12

[jimmywarting]

Purpose

Have created a beta branch and tough to start working on it already

Changes

• update ci workflow to only test v14.17 and above
• created a v4 limits + upgrade doc

Additional information

The documentation in v4 upgrade is changes to expect to come, they are not yet fixed...

---

• I updated readme
• I created a upgrade guide
• I change CI workflow to only test node 14.17+
• start working on this.

---

• part of v4 Roadmap #1452

[jimmywarting]

Hoping i'm doing this correctly now @gr2m when starting of with the v4 milestone / beta

[gr2m]

Hoping i'm doing this correctly now @gr2m when starting of with the v4 milestone / beta

I'd add a "BREAKING CHANGE: drop support for Node 12" or similar to the commit message body when you squash & merge, otherwise this looks good :)

[jimmywarting]

seem like Semantic Pull Request linter didn't like that i used BREAKING CHANGE:

[gr2m]

seem like Semantic Pull Request linter didn't like that i used BREAKING CHANGE:

The BREAKING CHANGE: needs to go into the commit body, not the commit subject.

[gr2m]

No idea why the "Semantic Pull Request" app is still complaining :( I'd ignore it

When you squash, make sure make the commit something like

drop support for Node 12

BREAKING CHANGE: drop support for Node 12

with the BREAKING CHANGE: in the commit body

[github-actions]

🎉 This PR is included in version 4.0.0-beta.1 🎉

The release is available on:

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

Your semantic-release bot 📦🚀