Closed agatakrajewska closed 3 months ago
Dropping support for Node 16 is arguably a breaking change
Dropping support for Node 16 is arguably a breaking change
Yes absolutely! That is why I have marked it as a feat
commit, as I understand you can do that or alternatively add a BREAKING CHANGE
keyword to the commit. Do you think feat
is not sufficient?
Dropping support for Node 16 is arguably a breaking change
Yes absolutely! That is why I have marked it as a
feat
commit, as I understand you can do that or alternatively add aBREAKING CHANGE
keyword to the commit. Do you thinkfeat
is not sufficient?
I see, I need both. Updated!
:tada: This PR is included in version 4.0.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
What does this PR do?
We're pinning the
semantic-release
version to22.0.0
for thenode18
support.Dropping EOL
node16
.