Hi team,
GitHub will force all actions to run on Node.js 24 starting June 2, 2026, and the current
v1.x releases (latest v1.9.1) are running on Node.js 20.
The standard GitHub Actions have already shipped Node.js 24 versions:
- actions/checkout@v5
- actions/upload-artifact@v6
- actions/download-artifact@v7
However, all powerplatform-actions sub-actions (actions-install, who-am-i, export-solution,
import-solution, pack-solution, unpack-solution, branch-solution) still require Node.js 20.
This means that after June 2, workflows using powerplatform-actions will either:
- Break if the actions are incompatible with the forced Node.js 24 runtime, or
- Require users to opt out using ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true
(which is not a sustainable solution)
Questions:
- Are there plans to release a Node.js 24 compatible version before the deadline?
- Will this be a minor update to v1, or a new major version (v2)?
- Has the team tested the current v1.9.1 with FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true?
Any visibility on the timeline would be appreciated.
Thanks!
Hi team,
GitHub will force all actions to run on Node.js 24 starting June 2, 2026, and the current
v1.x releases (latest v1.9.1) are running on Node.js 20.
The standard GitHub Actions have already shipped Node.js 24 versions:
However, all powerplatform-actions sub-actions (actions-install, who-am-i, export-solution,
import-solution, pack-solution, unpack-solution, branch-solution) still require Node.js 20.
This means that after June 2, workflows using powerplatform-actions will either:
(which is not a sustainable solution)
Questions:
Any visibility on the timeline would be appreciated.
Thanks!