You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Release 1.2.7 changes to require enginenode >= 18 AND peerDependencies: semantic-release >= 20.1.0, this is (at least in my eyes) a breaking change. Because before nodejs 12 and everything would still work perfectly fine, but now package managers may automatically update to the latest patch version, likely yelling at you and maybe even exiting with a non-0 exit code because it couldnt satisfy the requirements
Consider removing that release and release a 2.0.0 instead, or at the very least a 1.3.0
The text was updated successfully, but these errors were encountered:
also just noticed that 1.2.4 and 1.2.1 are also breaking changes, because before (1.2.3) it works with older semantic-release versions (like 19.0.5) but not anymore
1.2.1 (2831e9e) change to use lodash-es, which does not load correctly in semantic-release-replace-plugin with semantic-release 19.0.5 and 1.2.4 also does not work for the same reason (module being converted to ESM)
though the same would apply to @google/semantic-release-replace-plugin
Release
1.2.7
changes to requireengine
node >= 18
ANDpeerDependencies: semantic-release >= 20.1.0
, this is (at least in my eyes) a breaking change. Because before nodejs 12 and everything would still work perfectly fine, but now package managers may automatically update to the latest patch version, likely yelling at you and maybe even exiting with a non-0 exit code because it couldnt satisfy the requirementsConsider removing that release and release a
2.0.0
instead, or at the very least a1.3.0
The text was updated successfully, but these errors were encountered: