Upgrade action to node.js 24
- Dominant language
- JavaScript
- Stars
- 11
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Hey everyone,
do you plan to upgrade the action to native node.js 24? Github enforces node 24 with June 2026, so it would be nice if you natively support this.
By using the action right now you get warnings issued like
```
Warning: Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dapr/setup-dapr@8d980918fd43a2765c143ce7f687665b2d46a6b9. 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. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
```
BR Daniel
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue does not name a file or test. Start by locating the action's runtime declaration and existing validation workflow in the repository, then check how the action is packaged and tested. Done means the action natively runs on Node.js 24 without the reported Node.js 20 deprecation warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript, node.js
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100