Skip to content

tools: use lts node in notify-on-push workflow#63084

Merged
nodejs-github-bot merged 1 commit intonodejs:mainfrom
nsinfoPRO:fix/notify-on-push-workflow-set-node-lts
May 4, 2026
Merged

tools: use lts node in notify-on-push workflow#63084
nodejs-github-bot merged 1 commit intonodejs:mainfrom
nsinfoPRO:fix/notify-on-push-workflow-set-node-lts

Conversation

@nsinfoPRO
Copy link
Copy Markdown
Contributor

Without pinning Node.js, the runner defaults to Node 20 and npx falls back to [email protected] instead of 6.0.0 (requires Node 22+). Version 5 doesn't recognise the ffi subsystem, causing false invalid-commit alerts.

Fixes: #63070

@nodejs-github-bot
Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/actions

@nodejs-github-bot nodejs-github-bot added the meta Issues and PRs related to the general management of the project. label May 2, 2026
Comment thread .github/workflows/notify-on-push.yml
MikeMcC399

This comment was marked as outdated.

Comment thread .github/workflows/notify-on-push.yml Outdated
Without pinning Node.js, the runner defaults to Node 20 and npx falls
back to [email protected] instead of 6.0.0 (requires
Node 22+). Version 5 does not recognise the ffi subsystem, causing
false invalid-commit alerts.

Signed-off-by: Nenad Spasenic <[email protected]>
@nsinfoPRO nsinfoPRO force-pushed the fix/notify-on-push-workflow-set-node-lts branch from 60167cf to 6c9f340 Compare May 3, 2026 16:12
@aduh95 aduh95 added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label May 3, 2026
@aduh95 aduh95 added the commit-queue Add this label to land a pull request using GitHub Actions. label May 4, 2026
@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label May 4, 2026
@nodejs-github-bot nodejs-github-bot merged commit 6ef8dc8 into nodejs:main May 4, 2026
21 checks passed
@nodejs-github-bot
Copy link
Copy Markdown
Collaborator

Landed in 6ef8dc8

@MikeMcC399
Copy link
Copy Markdown
Contributor

MikeMcC399 commented May 5, 2026

@nsinfoPRO

Congratulations for the successful PR, despite my incorrect comments! Sorry once again for that!

https://github.com/nodejs/node/actions/runs/25353511115/job/74337950931 for example shows that the workflow is correctly working in production and is pulling the v6, not v5 release of core-validate-commit.

Run echo "$COMMITS" | npx -q core-validate-commit -
npm warn exec The following package was not found and will be installed: [email protected]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author ready PRs that have at least one approval, no pending requests for changes, and a CI started. meta Issues and PRs related to the general management of the project.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

meta: notify-on-push workflow uses old [email protected]

5 participants