Update Dependencies, Migrate to Node 22

[nagilson]

VS Code 1.100.0 migrated from node 20 to node 22. We should stay aligned with VS Code. Because our binaries actually run under whichever version node in Code is. This can cause extreme issues such as a complete failure to load if the compiler or language feature changes, and we would not know for some time.

Switching the linting from Mac to Windows because I cant get permission to push native linux packages.

[nagilson]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[nagilson]

I think I needed to push a new update to run lint to the internal feed.

[Copilot]

Pull Request Overview

Align project dependencies and tooling with VS Code’s upgrade to Node 22 to prevent runtime mismatches and load failures.

• Bump Mocha to 11.7.0 across all packages
• Update extension version, VS Code engine requirement, and Node installer to 22.x
• Adjust root package.json to reference Node 22 and refresh CHANGELOG for upcoming 3.0.0 release

Reviewed Changes

Copilot reviewed 7 out of 17 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
vscode-dotnet-sdk-extension/package.json	Mocha upgraded to ^11.7.0
vscode-dotnet-runtime-library/package.json	Mocha upgraded to ^11.7.0
vscode-dotnet-runtime-extension/package.json	Version bumped to 2.3.7, VS Code engine to ^1.101.0, Mocha to ^11.7.0
vscode-dotnet-runtime-extension/CHANGELOG.md	Changelog sections reorganized for 3.0.0 and 2.3.7
sample/package.json	Mocha upgraded to ^11.7.0
pipeline-templates/install-node.yaml	Node.js installer version updated to '22.x'
package.json	Added Node ^22.15.1 dependency

Comments suppressed due to low confidence (3)

vscode-dotnet-runtime-extension/CHANGELOG.md:10

• The changelog order is confusing: a 3.0.0 entry appears before 2.3.7 and a repeated 2.3.6. Consider reordering entries in descending version chronology and removing duplicates to improve clarity.

## [3.0.0] - 2025-7

sample/package.json:136

• After upgrading Mocha to 11.7.0, add or update tests to cover any breaking changes or new behaviors introduced in this major version bump.

		"mocha": "^11.7.0",

package.json:23

• Declaring Node as a dependency is unconventional; you should specify supported Node versions under the engines field instead of listing it in devDependencies or dependencies.

		"node": "^22.15.1",

[nagilson]

Ah. Let me try to push mac native specific packages from a mac machine.

[nagilson]

I cant get a mac that has permission to push native packages, lets switch to linux 🤪

[nagilson]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[MiYanni]

These are the only images available to that agent pool:

ubuntu-latest isn't a valid image name.

[nagilson]

It looks like name did not get propagated to the pool object which caused the default pool provider of azure pipelines to be used, so this was a valid image name, but it should not have been using that pool provider. I think this has been fixed now.

[nagilson]

I found the doc link to the images. I wish that it was better explained which section is for which pool, since there is no section for the netcore public pool, only the external test pooling in general 🤔

[MiYanni]

This, absolutely, should not be done. We should never use external Windows images. We use external macOS images because we don't have internal macOS agents.

[nagilson]

There is further logic that was already utilizing this, I don't recall how/why that is the case. I looked at the 1es migration PR and some of it may have been a migration tooling issue/pre-existing issue, and some of it may be due to the fact that name was not passed to the parameter pool object, thus causing the azure pipelines pool to be used. I think I've fixed all of those now, good call

[nagilson]

Thank you ✨