raised the peer requirement for semantic-release

[travi]

this is a breaking change to add to the list of breakages for this beta. using a normal merge already includes the token to consider as a breakage

before we decide to merge this though, i think this is a chance to consider semantic-release/semantic-release#2670 (comment) first. the options to decide between, as i see them, are:

• merge this PR that raises the peer requirement to the first beta of core that supports loading esm plugins, promote the beta of core still depending on a beta of the npm plugin, then raise the peer again to v21 that has been promoted to stable, and finally promote the npm plugin to stable
• backport the support for loading esm plugins to v20 of core, update the peer requirement here to the v20 version that supports esm plugins, promote the npm plugin to stable, promote core to stable

[gr2m]

backport the support for loading esm plugins to v20 of core, update the peer requirement here to the v20 version that supports esm plugins, promote the npm plugin to stable, promote core to stable

I'd prefer that option, unless you think it would be much more work? Maybe I miss something but think it should be fairly straight forward to do

[travi]

This is my preferred direction as well

[github-actions]

🎉 This PR is included in version 10.0.0-beta.3 🎉

The release is available on:

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

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 10.0.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀