[rush] Upgrade pnpm-sync-lib to 0.3.5 to unblock pnpm 11 support - #6103
Open
Martin Najemi (martinnaj) wants to merge 1 commit into
Open
Martin Najemi (martinnaj) wants to merge 1 commit into
Martin Najemi (martinnaj) wants to merge 1 commit into
Conversation
Author
|
@microsoft-github-policy-service agree |
Martin Najemi (martinnaj)
force-pushed
the
fix-rush-upgrade-pnpm-sync-lib-0.3.5
branch
from
September 30, 2026 08:57
14547cf to
8d75373
Compare
Author
Martin Najemi (martinnaj)
force-pushed
the
fix-rush-upgrade-pnpm-sync-lib-0.3.5
branch
2 times, most recently
from
September 30, 2026 09:46
7d43407 to
c144fdc
Compare
Author
|
@microsoft-github-policy-service agree |
Martin Najemi (martinnaj)
force-pushed
the
fix-rush-upgrade-pnpm-sync-lib-0.3.5
branch
3 times, most recently
from
October 2, 2026 11:28
e5622bd to
f865bf8
Compare
Upgrades the pnpm-sync-lib dependency of @microsoft/rush-lib from 0.3.4 to 0.3.5, which adds pnpm 11 compatibility (see tiktok/pnpm-sync#45). Fixes microsoft#5971
Martin Najemi (martinnaj)
force-pushed
the
fix-rush-upgrade-pnpm-sync-lib-0.3.5
branch
from
October 2, 2026 11:33
f865bf8 to
5448afa
Compare
Author
|
Hi Ian Clanton-Thuon (@iclanton), can you please take a look at this? After rebasing, CI checks are still red 😓 |
This branch has not been deployed
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
1 participant
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.
Note
PR checks are expected to fail until 2026-09-01 15:37 UTC. CI installs packages through
packagefeedproxy.microsoft.io, which only serves releases more than 7 days old —pnpm-sync-lib@0.3.5was published on 2026-08-25 15:37 UTC, sorush installcurrently gets a 404 for its tarball. Re-running the checks after that time should pass.Summary
Rush currently fails when used with pnpm v11:
This is caused by the
pnpm-sync-libdependency of@microsoft/rush-lib, which rejected pnpm 11 in its version check (tiktok/pnpm-sync#45, related report: #5846). That was fixed upstream in tiktok/pnpm-sync#47 and released aspnpm-sync-lib0.3.5. This PR upgrades the dependency from 0.3.4 to 0.3.5 to unblock pnpm 11 support.Fixes #5971
Details
This is a version-only dependency bump — no Rush code changes:
pnpm-sync-libfrom0.3.4to0.3.5inlibraries/rush-lib/package.json.defaultandbuild-tests-subspacesubspaces viarush update.rush change(patch bump for@microsoft/rush).The upstream 0.3.5 release adds pnpm v11 detection while retaining lockfile v9 support and reuses the pnpm v10-compatible dependency path naming for v11, so it is backwards compatible with pnpm 8.x–10.x.
How it was tested
rush updateand confirmed the lockfiles resolvepnpm-sync-lib@0.3.5cleanly across both subspaces.