build: update pnpm to v10.33.2

[angular-robot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	10.33.0 → 10.33.2

---

• If you want to rebase/retry this PR, check this box

---

Release Notes

pnpm/pnpm (pnpm)

v10.33.2: pnpm 10.33.2

Compare Source

Patch Changes

• Globally-installed bins no longer fail with ERR_PNPM_NO_IMPORTER_MANIFEST_FOUND when pnpm was installed via the standalone @pnpm/exe binary (e.g. curl -fsSL https://get.pnpm.io/install.sh | sh -) on a system without a separate Node.js installation. Previously, when which('node') failed during pnpm add --global, pnpm fell back to process.execPath, which in @pnpm/exe is the pnpm binary itself — and that path was baked into the generated bin shim, causing the shim to invoke pnpm instead of Node #​11291, #​4645.

• Fix an infinite fork-bomb that could happen when pnpm was installed with one version (e.g. npm install -g pnpm@A) and run inside a project whose package.json selected a different pnpm version via the packageManager field (e.g. pnpm@B), while a pnpm-workspace.yaml also existed at the project root.

  The child's environment is now forced to manage-package-manager-versions=false (v10) and pm-on-fail=ignore (v11+), which disables the package-manager-version handling in whichever pnpm runs as the child.

  Fixes #​11337.

Platinum Sponsors

Gold Sponsors

v10.33.1: pnpm 10.33.1

Compare Source

Patch Changes

• When a project's packageManager field selects pnpm v11 or newer, commands that v10 would have passed through to npm (version, login, logout, publish, unpublish, deprecate, dist-tag, docs, ping, search, star, stars, unstar, whoami, etc.) are now handed over to the wanted pnpm, which implements them natively. Previously they silently shelled out to npm — making, for example, pnpm version --help print npm's help on a project with packageManager: pnpm@11.0.0-rc.3 #​11328.

Platinum Sponsors

Gold Sponsors

[angular-robot]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: undefined

Command failed: pnpm update-generated-files
Computing main repo mapping: 
Loading: 
Loading: 1 packages loaded
Analyzing: target //ng-dev:npm_package (2 packages loaded, 0 targets configured)
Analyzing: target //ng-dev:npm_package (2 packages loaded, 0 targets configured)

Analyzing: target //ng-dev:npm_package (491 packages loaded, 7130 targets configured)

INFO: Analyzed target //ng-dev:npm_package (682 packages loaded, 7871 targets configured).
INFO: Found 1 target...
Target //ng-dev:npm_package up-to-date:
  dist/bin/ng-dev/npm_package
INFO: Elapsed time: 2.709s, Critical Path: 0.06s
INFO: 1 process: 1955 action cache hit, 1 internal.
INFO: Build completed successfully, 1 total action
ng-dev misc update-generated-files

Automatically discover all bazel generated file targets and update them.

Options:
  --version  Show version number                                                                               [boolean]
  --help     Show help                                                                                         [boolean]

Loading: 0 packages loaded
ERROR: invalid target name 'kind(esbuild, //...) intersect attr(name, '_generated$', //...)': target names may not contain '//' path separators

Exit code: 1.
Writing full log to /tmp/renovate/repos/github/angular/dev-infra/.ng-dev.err-1777031719692.log

[gemini-code-assist]

Code Review

This pull request updates the pnpm version from 10.33.0 to 10.33.1 across the repository, including updates to package.json files and Bazel module configurations with corresponding integrity hashes. I have no feedback to provide.