fix(deps): upgrade pnpm to v11 with versioned patch keys#709
Merged
Conversation
pnpm v11 requires version-qualified keys in patchedDependencies and uses a new lockfile format. The old patch context no longer matched isomorphic-git@1.38.1 (upstream changed node/default exports to node+default conditions), so the patch was regenerated using pnpm patch-commit to restore explicit import/require conditions for bundler compatibility. Also approves esbuild post-install script, which pnpm v11 now gates behind allowBuilds.
This was referenced May 28, 2026
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.
Summary
packageManagerfrompnpm@10.33.4topnpm@11.1.3in rootpackage.jsonpatchedDependencieskey fromisomorphic-gittoisomorphic-git@1.38.1(pnpm v11 requires version-qualified patch keys)allowBuilds: esbuild: truetopnpm-workspace.yaml(pnpm v11 gates post-install scripts)isomorphic-git@1.38.1.patchviapnpm patch-commit— upstream changed its exports fromnode+defaulttoimport+requireconditions, so the old patch context no longer matched; this is a full regeneration against the current upstream, not a renameThe
Desktop relay-backed e2efailure in CI is a pre-existing flaky test unrelated to this upgrade.