Moved to PNPM v11+ && updated node 20 references to Node22 where appropriate#2640
Merged
Conversation
hillary-mutisya
approved these changes
Jul 10, 2026
Collaborator
Author
|
@copilot resolve the merge conflicts in this pull request |
…s in package.json and pnpm-workspace.yaml
Contributor
Resolved in commit
|
Commit 28f1d1b rewrote 301 tarball URLs to registry.npmjs.org, which CI's Azure Artifacts feed rejects (ERR_PNPM_TARBALL_URL_MISMATCH). The underlying problem was that the lockfile baked in volatile per-mirror hosts (ms-feed-N.pkgs.visualstudio.com), which are load-balanced and non-portable across dev and CI. Regenerate the lockfile from a fresh resolution so pnpm records only integrity hashes (no hardcoded tarball host). Tarballs now resolve against whatever registry .npmrc configures, so the same lockfile verifies on both developer machines and CI.
…m/microsoft/TypeAgent into dev/robgruen/pnpm_version_upgrade
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request updates the monorepo and container policies to require Node.js 22 (instead of Node.js 20) and upgrades pnpm to version 11. It also migrates and restructures pnpm configuration from
package.jsonintopnpm-workspace.yamlto align with pnpm v11 requirements. The most important changes are:Node.js and Docker Image Updates:
All references to the Node.js version in Dockerfiles, container policies, documentation, and tests have been updated from
node:20/node:20-slimtonode:22/node:22-slim, ensuring consistency and compatibility with Node.js 22 across the codebase. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]Documentation (
README.md,getting-started.md) has been updated to state Node.js 22+ as the required version. [1] [2]pnpm Upgrade and Configuration Migration:
package.json, and removed the deprecatedpnpmfield.package.jsonintopnpm-workspace.yamlusing the new pnpm v11 syntax (allowBuilds, etc.), ensuring compatibility with the latest pnpm and improving configuration clarity.These changes ensure the project is using the latest supported Node.js and pnpm versions, and that containerized and policy-based execution environments are consistent and up-to-date.…opriate.