[Anthony Kim (anthonykim1)]

Unblocks: #995

• Raise the node-gyp development dependency from ^11.4.2 to ^12.1.0 and refresh its locked dependency graph.
• Use the first node-gyp release that recognizes Visual Studio 2026 (18.x), which is the only Visual Studio version on the current Windows ARM runner image.
• Add min-release-age=7 to .npmrc so newly published transitive dependencies have a week to reach the build feeds before npm selects them.
• Re-resolve undici to 6.29.0, avoiding the newer 6.29.1 tarball that is not yet available from the Monaco npm feed.
• Keep the existing CI matrix unchanged so windows-11-arm continues to verify the native build on ARM64.
• Stay on node-gyp 12 to retain Node.js 20 support instead of adopting node-gyp 13's narrower engine range.

---

Inspirations from:

• The minimum version comes from node-gyp's Visual Studio 2026 support, first released in node-gyp 12.1.0.
• Native Windows ARM coverage remains in node-pty's build-test matrix, and dependency installation continues through npm ci.

[Robo (deepak1556)]

Can we drop the node-gyp dependency and rely on the bundled version from npm, our current use cases can be switched to it and avoids developer churn in managing this dependency. You can make engine requirements strict on the package manifest to support VS 2026