microsoft / microsoft/powerplatform-actions

GitHub will force all actions to run on Node.js 24

Open
#684 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
301
Forks
88
PR merge metrics
No merged PRs in 30d

Description

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:

  1. Break if the actions are incompatible with the forced Node.js 24 runtime, or
  2. 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!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the seven named powerplatform-actions sub-actions and how the current v1.9.1 releases specify their Node.js runtime. Start by testing v1.9.1 with FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true. Done means the affected actions have a tested Node.js 24-compatible release before June 2, 2026, with the v1 or v2 version path documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, node.js, typescript
Domain
ci-cd, devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.