Update Node.js to v24.14.x and npm to v11.11.0 across build infrastructure by Copilot · Pull Request #66173 · dotnet/aspnetcore

Copilot · 2026-04-06T16:48:00Z

Update Node.js to v24.14.x and npm to v11.11.0 across build infrastructure

You've read the Contributor Guide and Code of Conduct.
You've included unit or integration tests for your change, where applicable.
You've included inline docs for your change, where applicable.
There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.

Upgrades Node.js from v20.x to v24.14.x and npm from v9.3.1 to v11.11.0 across all build infrastructure. Adds 3-day minimum release age for npm packages.

Description

Azure Pipelines Build Infrastructure

Updated NodeTool@0 tasks in .azure/pipelines/jobs/default-build.yml (2 instances) and .azure/pipelines/ci.yml to install Node 24.14.x

GitHub Actions Workflows

Updated setup-node tasks in .github/workflows/validate-npm-package-lock-json.yml, .github/workflows/update-jquery-validate.yml, and .github/workflows/markdownlint.yml to use Node 24.14.x

Package Requirements

Set engines in package.json to require node >=24.14.1 and npm >=11.11.0
Added min-release-age=3d to .npmrc to delay package adoption by 3 days after publication

Security

Added permissions: contents: read block to .github/workflows/validate-npm-package-lock-json.yml to follow GitHub Actions security best practices

All Node.js versions are pinned to 24.14.x to ensure builds always meet the minimum requirement (>=24.14.1) and are reproducible.

…npmrc Agent-Logs-Url: https://github.com/dotnet/aspnetcore/sessions/55ceeb17-c830-4b8e-822f-8baeb2098c14 Co-authored-by: javiercn <6995051+javiercn@users.noreply.github.com>

Copilot

Pull request overview

Updates the repo’s JavaScript toolchain baseline by moving build infrastructure to Node.js 24 and npm 11, and adds an npm configuration intended to delay adoption of very recent package releases.

Changes:

Bump package.json engine requirements to Node >=24.14.1 and npm >=11.11.0.
Add min-release-age=3d to .npmrc.
Update Azure Pipelines NodeTool@0 steps to install Node 24.x.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 5 comments.

File	Description
package.json	Raises declared minimum Node/npm versions via `engines`.
.npmrc	Adds a minimum release age policy for npm package installs.
.azure/pipelines/jobs/default-build.yml	Updates NodeTool tasks from 20.x to 24.x in default build jobs.
.azure/pipelines/ci.yml	Updates the CI pre-step NodeTool task from 20.x to 24.x.

Copilot · 2026-04-06T16:50:54Z

.azure/pipelines/jobs/default-build.yml

+          displayName: Install Node 24.x
          inputs:
-            versionSpec: 20.x
+            versionSpec: 24.x


versionSpec: 24.x can resolve to a Node 24 release lower than the minimum required by package.json (>=24.14.1). To ensure builds always satisfy the declared engine requirement and are reproducible, pin the pipeline NodeTool versionSpec to at least 24.14.1 (e.g., 24.14.1 or 24.14.x).

@copilot update as necessary

Updated all NodeTool versionSpec to 24.14.x to ensure builds satisfy the minimum requirement (>=24.14.1). Also updated GitHub Actions workflows to use the same pinned version. Changes in commit a38f236.

@copilot why would this resolve a lower version?

we recently bumped to 24.x in dotnet/dotnet@c2e6a4e and this installs 24.14.1

The concern was that 24.x could theoretically resolve to any 24.x version (e.g., 24.0.0, 24.1.0) when new agent images are released, potentially below the package.json requirement of >=24.14.1. However, if Azure Pipelines NodeTool@0 with 24.x is already reliably installing 24.14.1+ (as you've confirmed), then 24.x would be sufficient. The change to 24.14.x provides more explicit alignment with the minimum version and prevents any edge cases, but either approach should work in practice if the tool consistently resolves to recent patch versions.

Copilot · 2026-04-06T16:50:54Z

.azure/pipelines/jobs/default-build.yml

+          displayName: Install Node 24.x
          inputs:
-            versionSpec: 20.x
+            versionSpec: 24.x


versionSpec: 24.x can install a Node 24 version below the repo’s declared minimum (>=24.14.1 in package.json). Pin NodeTool to 24.14.1 (or 24.14.x) so the build reliably uses a compatible Node version.

Copilot · 2026-04-06T16:50:55Z

.azure/pipelines/ci.yml

+              displayName: Install Node 24.x
              inputs:
-                versionSpec: 20.x
+                versionSpec: 24.x


versionSpec: 24.x does not guarantee meeting the repo’s minimum Node engine (>=24.14.1). Pin NodeTool to 24.14.1 (or 24.14.x) to avoid intermittent failures when the latest 24.x is below the required patch level.

Copilot · 2026-04-06T16:50:55Z

package.json

+    "node": ">=24.14.1",
+    "npm": ">=11.11.0"


The PR description says the engines field “enforce[s]” node/npm versions, but npm won’t actually block installs based on engines unless engine-strict=true (or a CI check) is in place. If enforcement is intended, add an explicit validation step / config; otherwise consider rewording the description to “document/require”.

Copilot · 2026-04-06T16:50:55Z

.azure/pipelines/ci.yml

+              displayName: Install Node 24.x
              inputs:
-                versionSpec: 20.x
+                versionSpec: 24.x


This PR is described as updating Node “across build infrastructure”, but there are GitHub Actions workflows still pinned to Node 20.x (e.g., .github/workflows/validate-npm-package-lock-json.yml, .github/workflows/update-jquery-validate.yml). If those workflows should follow the repo-wide Node baseline, update them too or clarify that only Azure Pipelines is in scope.

Agent-Logs-Url: https://github.com/dotnet/aspnetcore/sessions/f3d02514-43ef-48f7-8ac9-04f4ad78e1f8 Co-authored-by: javiercn <6995051+javiercn@users.noreply.github.com>

akoeplinger · 2026-04-06T17:15:22Z

package.json

  "engines": {
-    "node": ">=20.9.0",
-    "npm": ">=9.3.1"
+    "node": ">=24.14.1",


@javiercn can you please check whether azurelinux has 24.14? otherwise this will break the VMR build as we use node from AZL packages there

we checked and the AZL image has node 24.13.0 and npm 11.6.2 so this needs some updates

Update Node.js to v24.x and npm to v11.11.0, add min-release-age to .…

a0c7723

…npmrc Agent-Logs-Url: https://github.com/dotnet/aspnetcore/sessions/55ceeb17-c830-4b8e-822f-8baeb2098c14 Co-authored-by: javiercn <6995051+javiercn@users.noreply.github.com>

Copilot AI assigned Copilot and javiercn Apr 6, 2026

Copilot created this pull request from a session on behalf of javiercn April 6, 2026 16:48 View session

javiercn marked this pull request as ready for review April 6, 2026 16:48

javiercn requested review from a team and wtgodbe as code owners April 6, 2026 16:48

Copilot AI review requested due to automatic review settings April 6, 2026 16:48

Copilot started reviewing on behalf of javiercn April 6, 2026 16:49 View session

github-actions bot added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Apr 6, 2026

Copilot AI reviewed Apr 6, 2026

View reviewed changes

wtgodbe approved these changes Apr 6, 2026

View reviewed changes

Copilot started work on behalf of javiercn April 6, 2026 17:02 View session

Copilot AI and others added 2 commits April 6, 2026 17:06

Pin Node.js version to 24.14.x across all pipelines and workflows

a38f236

Agent-Logs-Url: https://github.com/dotnet/aspnetcore/sessions/f3d02514-43ef-48f7-8ac9-04f4ad78e1f8 Co-authored-by: javiercn <6995051+javiercn@users.noreply.github.com>

Add permissions block to validate-npm-package-lock-json workflow

fd72146

Agent-Logs-Url: https://github.com/dotnet/aspnetcore/sessions/f3d02514-43ef-48f7-8ac9-04f4ad78e1f8 Co-authored-by: javiercn <6995051+javiercn@users.noreply.github.com>

Copilot AI changed the title ~~Update Node.js to v24.x and npm to v11.11.0 across build infrastructure~~ Update Node.js to v24.14.x and npm to v11.11.0 across build infrastructure Apr 6, 2026

Copilot AI requested a review from javiercn April 6, 2026 17:08

Copilot stopped work on behalf of javiercn due to an error April 6, 2026 17:08
The "Build solution" custom setup step from your .github/workflows/copilot-setup-steps.yml file failed.

akoeplinger reviewed Apr 6, 2026

View reviewed changes

Copilot started work on behalf of akoeplinger April 6, 2026 17:18 View session

Copilot stopped work on behalf of akoeplinger due to an error April 6, 2026 17:24
The "Build solution" custom setup step from your .github/workflows/copilot-setup-steps.yml file failed.

Copilot AI requested a review from akoeplinger April 6, 2026 17:24

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update Node.js to v24.14.x and npm to v11.11.0 across build infrastructure#66173

Update Node.js to v24.14.x and npm to v11.11.0 across build infrastructure#66173
Copilot wants to merge 3 commits intomainfrom
copilot/update-infrastructure-yaml

Copilot AI commented Apr 6, 2026 •

edited

Loading

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Apr 6, 2026

Uh oh!

javiercn Apr 6, 2026

Uh oh!

Copilot AI Apr 6, 2026

Uh oh!

akoeplinger Apr 6, 2026 •

edited

Loading

Uh oh!

Copilot AI Apr 6, 2026

Uh oh!

Copilot AI Apr 6, 2026

Uh oh!

Copilot AI Apr 6, 2026

Uh oh!

Copilot AI Apr 6, 2026

Uh oh!

Copilot AI Apr 6, 2026

Uh oh!

akoeplinger Apr 6, 2026

Uh oh!

akoeplinger Apr 6, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Conversation

Copilot AI commented Apr 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Update Node.js to v24.14.x and npm to v11.11.0 across build infrastructure

Description

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Apr 6, 2026

Choose a reason for hiding this comment

Uh oh!

javiercn Apr 6, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 6, 2026

Choose a reason for hiding this comment

Uh oh!

akoeplinger Apr 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 6, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 6, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 6, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 6, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 6, 2026

Choose a reason for hiding this comment

Uh oh!

akoeplinger Apr 6, 2026

Choose a reason for hiding this comment

Uh oh!

akoeplinger Apr 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Copilot AI commented Apr 6, 2026 •

edited

Loading

akoeplinger Apr 6, 2026 •

edited

Loading

akoeplinger Apr 6, 2026 •

edited

Loading