feat: update node version to 20

[enell]

Type of Change

• New feature
• Bug fix
• Documentation
• Refactor
• Chore

Resolves

• Fixes Incompatibility with semantic-release >v20 #168

Describe Changes

Node20 is being rolled out on github runnes

[MikeMcC399]

@enell

I would consider this a breaking change leading to a new major version bump, not simply a chore:.

Also the documentation would need updating, for instance: https://github.com/cycjimmy/semantic-release-action#semantic_version

[enell]

Yes you are correct. But is is a fix or feat?

[MikeMcC399]

Hopefully @cycjimmy will get involved and assist with the PR!

[Alegrowin]

@enell I went a little ahead and upgraded to semantic release 21 and node 20 as a default everywhere.

https://github.com/enell/semantic-release-action/pull/1/files

[cycjimmy]

I've been a bit busy with my current job and will probably attempt a new upgrade version next week.
The new version will be a BREAKING CHANGE. If you are trying to upgrade, you can submit using the feat keyword and add BREAKING CHANGE to the commit message footer.

[MikeMcC399]

@enell

You need to have the following text included literally in your commit:

BREAKING CHANGE:

and this would be

feat:

not simply

chore!:

I'm just echoing what @cycjimmy already wrote in #171 (comment), in case it was not clear to you.

[enell]

@MikeMcC399 Just updated

[github-actions]

🎉 This PR is included in version 4.0.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀

[cycjimmy]

This PR has been updated to the main branch. The new version is v4.
Thanks for your contributions.