Skip to content

Bump node from 20 to 24#1631

Closed
bohdanhusak wants to merge 2 commits intogithub:mainfrom
bohdanhusak:chore/node-24
Closed

Bump node from 20 to 24#1631
bohdanhusak wants to merge 2 commits intogithub:mainfrom
bohdanhusak:chore/node-24

Conversation

@bohdanhusak
Copy link

Summary

Update dependabot-action to run using node24 instead of node20.

Details

Since node20 is deprecated, dependabot runs trigger following deprecation message:

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: github/dependabot-action@main. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true.

Github post about Node.js 20 deprecation: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

I have updated .nvmrc and action.yml for this PR. Other changes were generated by npm run package.

@bohdanhusak bohdanhusak requested a review from a team as a code owner March 13, 2026 01:04
@Nishnha
Copy link
Member

Nishnha commented Mar 16, 2026

We may want to release this as a standalone major release like we did for v2 with node 16.

Copy link
Member

@jeffwidman jeffwidman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for swinging by to contribute!

This action is used by multiple versions of the GitHub Enterprise Server (GHES).

We're blocked on updating to node24 until the (estimated) October, 2026 deprecation of GHES 3.18.4... that's the newest version of GHES that doesn't yet support node24.

If we really had to, we could upgrade and leave those old versions in the dust, but it'd create some pain and agony if we have to do any backports etc, so it's probably simplest if we wait til then to make this jump.

@bohdanhusak
Copy link
Author

Hi @jeffwidman, this makes sense 👍

In this case will close current PR and node24 update can be addressed when the time is right.

Thank you!

@bohdanhusak bohdanhusak deleted the chore/node-24 branch March 17, 2026 12:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants