I think I made a fundamental mistake in 2020 when I designed the release pipeline by managing the dependencies through the devDependencies in package.json.Node 12 is no longer maintained by Node, and IMHO we should just drop it…but this is bigger, we have same release and pr testing workflows everywhere, we need to agree on dropping Node 12 everywhere, and the ones that do not agree, will need to maintain their custom workflows 🤷🏼.There are 2 threads in this issue, 2 different challenges: Worked like a charm…until I thought, I’ll check with Node 12…and it failed as latest semantic-release do not support Node 12 I tried to solve peer dependency issues - it was good. Now wait, why these issues did not pop up before? it is because according to my knowledge early versions of node 16 had npm 7 while the latest versions include npm 8. Easy, just bump the packageĪnd then the problem starts, we get a bunch of issues related to peerDependency in release-related plugins as they are referring wrong versions, all that stuff. When we switch to 16, which we should do anyway, we get an issue that semantic-release must be bumped because the version doesn’t match the Node release. This is easy, we can just switch to 16 and 15 is anyway not LTS. We run them at the moment on nodejs 12,14,15 and 15 is causing issues.

We started having a problem with tests in this project. Where do I even start…got for sure triggered by failing test in

Npm version