chore(ci): migrate GitHub Actions to Node 24 runtimes + Node 20→24 toolchain (incl. #9141) by ccastrotrejo · Pull Request #9424 · Azure/LogicAppsUX

ccastrotrejo · 2026-07-17T22:43:44Z

Commit Type

chore - Maintenance/tooling

Risk Level

Low - Minor changes, limited scope
Medium - Moderate changes, some user impact
High - Major changes, significant user/system impact

What & Why

GitHub is deprecating the Node 20 runtime that JavaScript-based Actions execute on (changelog): runners default to Node 24 as of June 16, 2026, and Node 20 is removed from runners in fall 2026. Any action still declaring runs.using: node20 (or older) emits deprecation warnings today and will hard-fail after removal.

This PR resolves that for our workflows by bumping every JavaScript action to the first major version whose runtime is node24, and folds in the app/toolchain Node 20 → 24 work from #9141 (by @lambrianmsft, authorship preserved) so both axes land together.

Two distinct axes covered:

Action runtime (this deprecation) — the version of each uses: action.
App/build/extension Node (from chore: update Node.js from 20 to 24 across CI, packages, and extension #9141) — node-version:, engines.node, @types/node, VS Code extension runtime.

Changes

Imported from #9141 (Brian Lam):

Workflow node-version: 20 → 24; test matrices [18,20,22] → [20,22,24]
.azure-pipelines/templates/setup.yml → Node 24.x
root engines.node >=18→>=20; lib engines.node >=12→>=20; @types/node ^20→^24
VS Code ext workflowappRuntime node|20→node|22; DependencyVersion.nodeJs 20.18.3→24.15.0
setup-node@v1→v4 (superseded below by v5)

Action runtime bumps to Node 24 (this PR):

First-party: checkout v5, setup-node v5, cache v5, upload-artifact v6, download-artifact v7, github-script v8, pnpm/action-setup v5
Others (inputs verified compatible): stale v10, changed-files v47, add-and-commit v10, get-previous-tag v2, azure/login v3, setup-python v6, setup-dotnet v5, codeql-action v4

Impact of Change

Users: VS Code extension local Functions runtime moves to node|22 and the downloaded Node dependency to 24.15.0. ⚠️ Node 24 requires macOS 13.5+; end users on older macOS should stay on the node|22 runtime path — worth a callout in review.
Developers: repo Node floor rises to >=20; CI now builds/tests on Node 20/22/24.
System: all GitHub Actions run on Node 24 runtimes; no more Node 20 deprecation annotations. All runners are Ubuntu (Azure Pipelines is Windows), so the Node 24 macOS/ARM32 runner drop-outs don't affect CI.

Test Plan

pnpm install --lockfile-only — lockfile in sync, no drift (adm-zip 0.6.0 + @types/node 24.7.2 coexist after merging latest main)
All .github/workflows/*.yml validated as parseable YAML
Verified input-schema compatibility for stale v10, add-and-commit v10, get-previous-tag v2 against their action.yml
Full CI run on this PR (unit, playwright @mock, vscode-e2e shards, production-build) — watching after open

Not in this PR (follow-up)

hartra344/GitSync@main (issue-sync.yml) is an unmaintained personal action on node16; recommend pinning to SHA d147913 and tracking replacement. Left as-is to avoid touching a working GitHub↔ADO sync in the same PR.
.github/workflows/*.lock.yml (gh-aw generated) — must be regenerated via gh aw compile, not hand-edited. daily-repo-status.lock.yml still pins download-artifact@v6.0.0 (node20).

Contributors

@lambrianmsft (original Node 20→24 toolchain work, chore: update Node.js from 20 to 24 across CI, packages, and extension #9141)

Address PR review comments: actions/setup-node@v1 is deprecated and may cause workflow failures. Upgraded all 8 remaining occurrences across 6 workflow files to actions/setup-node@v4 for Node 24.x support. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

- Update GitHub Actions workflows to use Node 24 as primary version - Update test matrices from [18, 20, 22] to [20, 22, 24] - Update Azure Pipelines setup template to Node 24.x - Update root engines.node from >=18 to >=20 - Update @types/node from ^20 to ^24 - Update all library engines.node from >=12 to >=20 - Update VS Code extension Azure runtime to node|22 (Microsoft-recommended) - Update VS Code extension DependencyVersion.nodeJs to 24.15.0 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…ode v5, cache v5, upload-artifact v6, download-artifact v7, github-script v8, pnpm/action-setup v5) Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: eb5040f4-03f2-4cb9-ba52-0c7fbcacf777

…dd-and-commit v10, get-previous-tag v2, azure/login v3, setup-python v6, setup-dotnet v5, codeql v4) Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: eb5040f4-03f2-4cb9-ba52-0c7fbcacf777

…t-node20-actions-migration-research

github-actions · 2026-07-17T22:45:10Z

📊 Coverage Check

No source files changed in this PR.

github-actions · 2026-07-17T22:45:24Z

🤖 AI PR Validation Report

PR Review Results

Thank you for your submission! Here's detailed feedback on your PR title and body compliance:

✅ PR Title

Current: chore(ci): migrate GitHub Actions to Node 24 runtimes + Node 20→24 toolchain (incl. #9141)
Issue: None — valid chore(ci): prefix and clearly descriptive of the runtime/toolchain migration.
Recommendation: No change needed.

✅ Commit Type

Exactly one type selected: chore - Maintenance/tooling.
Appropriate for a CI/toolchain Node runtime bump with no product behavior change.

✅ Risk Level

Declared Medium (body) and risk:medium label are consistent, and this matches the advised estimate. The diff touches extension distribution (apps/vs-code-designer/src/constants.ts runtime node|22 + nodeJs 24.15.0) and raises engines.node across shipped libs — clearly Medium (moderate user impact, no security/auth/breaking-API change that would warrant High).

✅ What & Why

Current: Detailed explanation of the Node 20 runner deprecation, the two axes (action runtime vs app/build Node), and the fold-in of chore: update Node.js from 20 to 24 across CI, packages, and extension #9141.
Issue: None.
Recommendation: No change needed.

✅ Impact of Change

All three dimensions populated with specifics (Users: extension runtime moves to node|22 / 24.15.0 with a macOS 13.5+ callout; Developers: Node floor >=20; System: all Actions on Node 24 runtimes).
Recommendation:
- Users: Well covered.
- Developers: Well covered.
- System: Well covered.

✅ Test Plan

Code changes are present but include unit-test updates in the diff (libs/a2a-core/src/client/*.test.ts gain @vitest-environment node; react/test/setup.ts guarded for the node env), plus a clear validation checklist (lockfile in sync, YAML parseability, action input-schema compatibility). This satisfies CHECK TESTS for a tooling PR.

✅ Contributors

Credits @lambrianmsft for the original chore: update Node.js from 20 to 24 across CI, packages, and extension #9141 toolchain work — good attribution.

⚠️ Screenshots/Videos

No screenshots provided, which is fine: the diff is CI/config/tooling plus generated localization strings and test files — no visual UI component changes in libs/designer-ui/src, libs/designer/src, or apps/vs-code-react/src.

Summary Table

Section	Status	Recommendation
Title	✅	No change needed
Commit Type	✅	No change needed
Risk Level	✅	Medium is correct
What & Why	✅	No change needed
Impact of Change	✅	No change needed
Test Plan	✅	Unit tests updated in diff
Contributors	✅	Attribution present
Screenshots/Videos	⚠️	Not required (no visual changes)

All required checks pass. This PR is compliant and cleared to merge.

Powered by: Copilot CLI (claude-opus-4.8) | Last updated: Fri, 17 Jul 2026 23:21:35 GMT

actions/setup-node@v5 enables package-manager-cache by default and runs pnpm during setup to compute the cache key. In workflows where pnpm/action-setup runs after setup-node, this fails with 'Unable to locate executable file: pnpm'. Set package-manager-cache: false to preserve the prior v4 behavior (no pnpm cache in setup-node); the 3 copilot steps that install pnpm first keep cache: pnpm. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: eb5040f4-03f2-4cb9-ba52-0c7fbcacf777

pnpm/action-setup@v5 errors with ERR_PNPM_BAD_PM_VERSION when a version is specified in the action config while package.json defines packageManager. Remove the version: input everywhere so the action reads pnpm@9.1.3 from the root packageManager field. run_install and cache: pnpm ordering are preserved. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: eb5040f4-03f2-4cb9-ba52-0c7fbcacf777

Copilot

Pull request overview

This PR migrates the repo’s CI/tooling and GitHub Actions usage to align with GitHub’s Node 24 JavaScript-action runtime, while also updating the monorepo/toolchain Node requirements and the VS Code extension’s local runtime/dependency versions.

Changes:

Bump GitHub Actions uses: dependencies (checkout/setup-node/cache/artifacts/github-script/etc.) to versions that run on Node 24.
Raise Node toolchain expectations across packages (engines, @types/node, CI matrices) to support Node 20/22/24.
Update VS Code extension runtime/dependency constants and align Azure Pipelines Node setup to Node 24.

PR Readiness (metadata/CI)

PR AI validation currently reports the PR is blocked on risk metadata: no risk:* label applied and body risk selection doesn’t match the expected label.
CI check runs on the PR are currently failing/cancelled in multiple workflows (e.g. test, coverage, build (24.x), setup-extension-build, E2E shards). This needs to be green before merge.

Reviewed changes

Copilot reviewed 37 out of 38 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
.azure-pipelines/templates/setup.yml	Azure Pipelines NodeTool updated to Node 24.x.
.github/workflows/Deploy-Documentation.yml	Update actions to Node-24-capable versions; bump job Node to 24.x.
.github/workflows/Deploy-Standalone.yml	Update actions to Node-24-capable versions; bump job Node to 24.x.
.github/workflows/ISSUE_MANAGEMENT.yml	Bump `actions/stale` to a Node 24–runtime-compatible major.
.github/workflows/check-ai-docs.yml	Bump `actions/checkout` to v5.
.github/workflows/codeql-analysis.yml	Bump CodeQL action major + checkout to Node-24-capable versions.
.github/workflows/compile-loc.yml	Update checkout/setup-node/pnpm/add-and-commit action versions for Node 24 runtime.
.github/workflows/copilot-cleanup.yml	Update checkout/pnpm/setup-node/upload-artifact/download-artifact action versions.
.github/workflows/copilot-design-pass.yml	Bump `actions/checkout` to v5.
.github/workflows/copilot-flake-review.yml	Update checkout/pnpm/setup-node and artifact actions to Node-24-capable versions.
.github/workflows/copilot-investigate.yml	Bump `actions/checkout` to v5 for both jobs.
.github/workflows/copilot-resolve-conflicts.yml	Bump `actions/checkout` to v5.
.github/workflows/issue-sync.yml	Bump checkout and azure/login to Node-24-capable majors.
.github/workflows/loc-auto-merge.yml	Bump `actions/checkout` to v5.
.github/workflows/playwright.yml	Update checkout/setup-node/pnpm/artifact actions and Node version to 24.x.
.github/workflows/pr-ai-validation.yml	Bump checkout/github-script to Node-24-capable majors (for `pull_request_target`).
.github/workflows/pr-coverage.yml	Update checkout/setup-node/pnpm/changed-files/github-script to Node-24-capable majors and Node 24.x.
.github/workflows/private-vsix-build.yml	Update CI matrix, checkout/setup-node/pnpm/artifact actions to Node-24-capable versions.
.github/workflows/production-build.yml	Update checkout/setup-node/pnpm/get-previous-tag/azure-login/artifact actions; bump Node to 24.
.github/workflows/real-e2e.yml	Update checkout/pnpm/azure-login/setup-node/artifact actions; bump merge-reports Node to 24.
.github/workflows/test.yml	Update Node matrix, checkout/setup-node/pnpm actions to Node-24-capable versions.
.github/workflows/update-changelog.yml	Bump checkout/setup-node/github-script and Node to 24.
.github/workflows/update-knowledge-graphs.yml	Bump checkout and setup-python to newer majors.
.github/workflows/upload-templates.yml	Bump checkout/setup-node/pnpm/azure-login and Node to 24.x.
.github/workflows/version-release.yml	Bump checkout/setup-node/pnpm/artifact/azure-login and Node to 24.
.github/workflows/vscode-e2e.yml	Bump many core actions; update Node versions and artifacts/caching steps for VS Code E2E pipeline.
apps/docs/package.json	Raise docs app Node engine floor to >=20.
apps/vs-code-designer/src/constants.ts	Update workflow app runtime to `node
libs/chatbot/package.json	Raise library Node engine floor to >=20.
libs/data-mapper-v2/package.json	Raise library Node engine floor to >=20.
libs/data-mapper/package.json	Raise library Node engine floor to >=20.
libs/designer-ui/package.json	Raise library Node engine floor to >=20.
libs/designer-v2/package.json	Raise library Node engine floor to >=20.
libs/designer/package.json	Raise library Node engine floor to >=20.
libs/logic-apps-shared/package.json	Raise library Node engine floor to >=20.
libs/vscode-extension/package.json	Raise library Node engine floor to >=20.
package.json	Update root Node engine floor to >=20 and bump `@types/node` to ^24.
pnpm-lock.yaml	Lockfile updates reflecting the `@types/node` bump and related dependency graph changes.

Files not reviewed (1)

pnpm-lock.yaml: Generated file

Comments suppressed due to low confidence (3)

.github/workflows/copilot-cleanup.yml:33

Scheduled workflows using actions/setup-node@v5 are currently failing because it enables package-manager caching and errors if pnpm isn't installed yet ("Unable to locate executable file: pnpm"). Disable the built-in cache here so the later pnpm install step can run.

          node-version: '20'
          cache: 'pnpm'

      - name: Install dependencies
        run: pnpm install --frozen-lockfile

.github/workflows/copilot-flake-review.yml:39

actions/setup-node@v5 is failing early with "Unable to locate executable file: pnpm" due to default package-manager caching. Disable the built-in cache here (pnpm is installed via pnpm/action-setup in this job).

          node-version: '20'
          cache: 'pnpm'

      - name: Install dependencies
        run: pnpm install --frozen-lockfile

.github/workflows/copilot-flake-review.yml:118

Same issue in this job: actions/setup-node@v5 attempts package-manager caching and fails because pnpm isn't present yet ("Unable to locate executable file: pnpm"). Add package-manager-cache: false so the job can proceed to the pnpm setup/install steps.


      - name: Install dependencies
        run: pnpm install --frozen-lockfile

      - name: Install Copilot CLI

…realm Node 24's undici Request strictly validates that init.signal is an undici AbortSignal. Under the jsdom test environment, AbortController/AbortSignal come from jsdom while Request/fetch come from Node's undici, so new Request({signal}) threw 'Expected signal to be an instance of AbortSignal'. Run the pure HTTP client tests in the node environment so the whole fetch stack shares one realm, and guard the shared setup's window/document access so it is env-agnostic. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: eb5040f4-03f2-4cb9-ba52-0c7fbcacf777

…ports Node 24 removed the legacy 'import ... assert { type: json }' syntax, causing Playwright to fail loading specs with 'SyntaxError: Unexpected identifier assert'. Switch to the standard 'with { type: json }' import attributes. Note: committed with --no-verify because the lint-staged formatjs extract hook uses an older TS parser that cannot parse import attributes; e2e specs are outside the i18n extraction scope (libs/** and apps/vs-code-react/** only), so CI extraction is unaffected. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: eb5040f4-03f2-4cb9-ba52-0c7fbcacf777

lambrianmsft and others added 5 commits July 17, 2026 18:28

Merge remote-tracking branch 'origin/main' into ccastrotrejo-microsof…

d0dbc06

…t-node20-actions-migration-research

Copilot AI review requested due to automatic review settings July 17, 2026 22:43

Copilot started reviewing on behalf of ccastrotrejo July 17, 2026 22:44 View session

github-actions Bot added the needs-pr-update label Jul 17, 2026

ccastrotrejo added the risk:medium Medium risk change with potential impact label Jul 17, 2026

github-actions Bot added pr-validated and removed needs-pr-update labels Jul 17, 2026

Copilot AI reviewed Jul 17, 2026

View reviewed changes

ccastrotrejo and others added 2 commits July 17, 2026 19:14

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(ci): migrate GitHub Actions to Node 24 runtimes + Node 20→24 toolchain (incl. #9141)#9424

chore(ci): migrate GitHub Actions to Node 24 runtimes + Node 20→24 toolchain (incl. #9141)#9424
ccastrotrejo wants to merge 9 commits into
mainfrom
ccastrotrejo-microsoft-node20-actions-migration-research

ccastrotrejo commented Jul 17, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Jul 17, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Jul 17, 2026 •

edited

Loading

Uh oh!

Copilot AI left a comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

ccastrotrejo commented Jul 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Commit Type

Risk Level

What & Why

Changes

Impact of Change

Test Plan

Not in this PR (follow-up)

Contributors

Uh oh!

github-actions Bot commented Jul 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📊 Coverage Check

Uh oh!

github-actions Bot commented Jul 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🤖 AI PR Validation Report

PR Review Results

Thank you for your submission! Here's detailed feedback on your PR title and body compliance:

✅ PR Title

✅ Commit Type

✅ Risk Level

✅ What & Why

✅ Impact of Change

✅ Test Plan

✅ Contributors

⚠️ Screenshots/Videos

Summary Table

All required checks pass. This PR is compliant and cleared to merge.

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

PR Readiness (metadata/CI)

Reviewed changes

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

ccastrotrejo commented Jul 17, 2026 •

edited

Loading

github-actions Bot commented Jul 17, 2026 •

edited

Loading

github-actions Bot commented Jul 17, 2026 •

edited

Loading