Test/validate node 16 for Renovate runtime

[rarkins]

What would you like Renovate to be able to do?

Use node 16 as runtime, and upgrade to it for official Renovate images.

If you have any ideas on how this should be implemented, please tell us here.

It should be pretty stable by now, so perhaps we can return to having a matrix of node 14 + 16 for a while until we migrate to testing only 16?

Is this a feature you are interested in implementing yourself?

No

[viceice]

sounds good, node v16 should be next lts on 2022-10-18

https://nodejs.org/en/about/releases/

[viceice]

npx will fail on npm v7

renovate/.github/workflows/build.yml

Line 208 in 53e3cb1

npx semantic-release --dry-run ${{env.DRY_RUN}}

Seen this on buildpack

[viceice]

• Stopped working with yarn mysticatea/npm-run-all#196

[redeyes2015]

I think this is related: mysticatea/npm-run-all#209

In short: due to how npx works since npm@7, npm-run-all does not work properly if invoked in npx.

The possible work-around for now seems to be:

1. avoid npx , use node_modules/.bin/the-command directly
2. use run-s --npm-path npm in every whererun-s/run-p/npm-run-all is used

[mcser]

I am a little confused what the issue is here. I tried to reproduce this by forking the project and configuring a pipeline in my repository using node 16 to try and dry-run semantic-release, and on my end it appears to be working (but refuses to release a version of your image, of course).

Run npx semantic-release --dry-run false
[12:56:39 PM] [semantic-release] › ℹ  Running semantic-release version 19.0.5
[12:56:39 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/github"
[12:56:39 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/exec"
[12:56:39 PM] [semantic-release] › ✔  Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
[12:56:39 PM] [semantic-release] › ✔  Loaded plugin "analyzeCommits" from "@semantic-release/exec"
[12:56:39 PM] [semantic-release] › ✔  Loaded plugin "verifyRelease" from "@semantic-release/exec"
[12:56:39 PM] [semantic-release] › ✔  Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
[12:56:39 PM] [semantic-release] › ✔  Loaded plugin "generateNotes" from "@semantic-release/exec"
[12:56:39 PM] [semantic-release] › ✔  Loaded plugin "prepare" from "@semantic-release/exec"
[12:56:39 PM] [semantic-release] › ✔  Loaded plugin "publish" from "@semantic-release/github"
[12:56:39 PM] [semantic-release] › ✔  Loaded plugin "publish" from "@semantic-release/exec"
[12:56:39 PM] [semantic-release] › ✔  Loaded plugin "addChannel" from "@semantic-release/github"
[12:56:39 PM] [semantic-release] › ✔  Loaded plugin "addChannel" from "@semantic-release/exec"
[12:56:39 PM] [semantic-release] › ✔  Loaded plugin "success" from "@semantic-release/github"
[12:56:39 PM] [semantic-release] › ✔  Loaded plugin "success" from "@semantic-release/exec"
[12:56:39 PM] [semantic-release] › ✔  Loaded plugin "fail" from "@semantic-release/github"
[12:56:39 PM] [semantic-release] › ✔  Loaded plugin "fail" from "@semantic-release/exec"
[12:57:31 PM] [semantic-release] › ✔  Run automated release from branch main on repository https://github.com/renovatebot/renovate.git
[12:57:31 PM] [semantic-release] › ℹ  The local branch main is behind the remote one, therefore a new version won't be published.

EDIT: Woops I just realized that I had dry-run false, I'll try it again with the flag set to true.

EDIT 2: Same result with dry run set to true.