ci: stop testing floating node alias

[astrochicken-hatch]

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and discussions and couldn’t find anything or linked relevant results below
• I made sure the docs are up to date
• I included tests (or that’s not needed)

Description of changes

Stop using the floating node alias in CI and test Node 24 explicitly in the main and canary jobs.

The current workflow resolves node-version: node to Node 25, which currently breaks this repo and the canary jobs inside yargs during test coverage runs. Pinning a stable supported release fixes the current CI failure without changing package code.

Evidence from failing PR run 22593660529:

• node-version: node resolved to v25.7.0
• npm test failed with ReferenceError: require is not defined in ES module scope in node_modules/yargs/yargs
• both canary jobs hit the same Node 25 failure

[github-actions]

Hi! It seems you removed the template which we require. Here are our templates (pick the one you want to use and click *raw* to see its source):

• pull-request-template.md

I won’t send you any further notifications about this, but I’ll keep on updating this comment, and hide it when done!

Thanks,
— bb

[ChristianMurphy]

Testing latest is intentional, it catches issues when new releases some out.

[astrochicken-hatch]

Makes sense, thanks for the clarification.

I dug into it locally and the failure might just be a Node 25.7.0 incompatibility in c8/yargs rather than a remark regression. Replacing node with 24 removes the intentional latest check, so this PR is the wrong fix for your CI setup.

Closing this out.

[github-actions]

Hi! This was closed. Team: If this was merged, please describe when this is likely to be released. Otherwise, please add one of the no/* labels.