build: update all non-major dependencies

[angular-robot]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@google/genai	2.28.0 → 2.29.1
@puppeteer/browsers (source)	3.2.3 → 3.2.4
@types/node (source)	24.19.1 → 24.19.2
pnpm (source)	12.10.1 → 12.11.2
prettier (source)	3.9.9 → 3.9.10
renovate (source)	44.145.2 → 44.156.1
selenium-webdriver (source)	4.50.0 → 4.51.0

---

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

---

Release Notes

googleapis/js-genai (@​google/genai)

v2.29.1

Compare Source

Bug Fixes

• concatenate output_text across multi-step model responses in a turn (567cc8a)

v2.29.0

Compare Source

Features

• accumulate streaming continuation usage metadata and expose initialPromptTokenCount (dbc961f)
• Add continuation_token to the Interactions interaction.status_update event. (a93776c)
• Add a CONTINUATION_REQUIRED Interaction status (754f71f)
• add billable token counts fields (839ffc2)
• Add startOffset/endOffset to Transcription and interimTranscriptTimestampEnabled to RealtimeInputConfig (bdbf156)
• Add usage in InteractionStatusUpdate events (8892aea)
• automatically consume the continuation token (98637d1)
• cli: update Speakeasy generator to v2.948.0, bump CLI to v0.4.2, and apply CLI overlay fixes (22d53ec)

Bug Fixes

• clear intermediate CONTINUATION finishReason in streaming continuation (22706af)
• do not record incomplete continuation stream turns in curated chat history (81c3c49)
• gemini-api-cli: remove unsupported 2.5 and 1.6 models from Interactions model options and CLI examples (1002720)
• js: do not set initial prompt token count for requests that do not use automatic consumption of continuation token (0885fb9)
• js: fix streaming continuation edge cases (stale token, AbortError, initialPromptTokenCount) (f3d10a6)
• Raise default HTTP timeouts so long-running requests aren't killed client-side (10e850c)
• resume streaming generation from the latest checkpoint continuation token on mid-stream errors or cutoffs (625ac2c)
• Update EnvironmentConfig.env schema to map keys to EnvVar or string. (8478e12)

puppeteer/puppeteer (@​puppeteer/browsers)

v3.2.4

Compare Source

pnpm/pnpm (pnpm)

v12.11.2: pnpm 12.11.2

Compare Source

This release fixes --workspace-concurrency=Infinity, filters set by an updateConfig hook, and store fetches with enable-modules-dir=false.

Patch Changes

• --workspace-concurrency=Infinity now runs workspace projects with no concurrency limit. It used to fail with invalid digit found in string #​16793.

• pnpm install and other recursive commands now apply the filter and filterProd that an updateConfig hook sets. They used to run on every workspace project #​16792.

• enable-modules-dir=false now also fetches the packages an install reuses from an existing lockfile, so the store holds every package the lockfile lists.

Platinum Sponsors

Gold Sponsors

v12.11.1: pnpm 12.11.1

Compare Source

This release fixes two ways pnpm install could fail, runs tools of any Rust release through pnx, and treats registry.npmjs.com as an alias of the npm registry.

Patch Changes

• pnpm install no longer fails when packageManager pins the pnpm version that is already running and the registry does not publish that version. pnpm warns and continues. A registry mirror that has not synced a release no longer blocks the commands of a project pinned to it.

• pnpm install no longer fails with ERR_PNPM_CMD_SHIM_CHMOD when node_modules/.bin holds a shim that another user created, if everyone can already execute it and it is not world-writable. This happens when several users share one checkout.

• enable-modules-dir=false (enableModulesDir: false through the Node.js addon) fetches the registry packages the host can install into the store again, as pnpm v10 did, while still writing nothing under node_modules. The setting exists for a node_modules that something else mounts from the store, such as a FUSE daemon, and that consumer no longer has to download each package on first access. A plain --lockfile-only run still fetches nothing.

• pnpm pack and pnpm publish no longer put .npmignore and .gitignore files in the tarball. A files entry that names one still ships it.

• pnpm now treats https://registry.npmjs.com/ as an alias of https://registry.npmjs.org/. Registry requests, credentials, and trusted publishing use the canonical hostname.

• pnx --package=rust@<channel> <tool> runs a tool of that Rust release, for example pnx --package=rust@nightly-2026-01-01 cargo build. pnpm installs the release with the components and targets from rust-toolchain.toml and the target of each --target argument.

• pnpm install now links agent skills for more coding agents. It detects the agent from ANTIGRAVITY_AGENT, COPILOT_AGENT, COPILOT_CLI, CODEX_THREAD_ID, CODEX_SANDBOX, AI_AGENT, and CLAUDE_CODE pnpm/tasks#116.

• When the registry rejects pnpm stage publish, the error message now starts with "Failed to stage package".

Platinum Sponsors

Gold Sponsors

v12.11.0: pnpm 12.11.0

Compare Source

This release adds Rust toolchain management, links the agent skills that dependencies ship, adds the permissions setting, and keeps the colors of streamed script output.

Minor Changes

• pnpm install now links the agent skills that direct dependencies ship under skills/<name>/SKILL.md into the project's agent skill directories, such as .claude/skills. A package's skills are linked only after you approve them with pnpm approve. The skills.dirs setting chooses the directories pnpm/rfcs#35.

  Added the permissions setting, which records what each dependency may do. Its build capability works like allowBuilds and takes precedence over it. pnpm approve-builds writes to permissions when pnpm-workspace.yaml already has it, and to allowBuilds otherwise.

  Added pnpm permissions, which lists the granted and denied permissions and the packages awaiting approval. pnpm approve reviews build scripts and agent skills in one prompt pnpm/rfcs#36.

• pnpm now installs and runs Rust toolchains.

  • With cargo.enabled, pnpm install installs the toolchain named in rust-toolchain.toml. pnpm verifies the release signature, stores the toolchain once per machine, and links it into .pnpm/rust. pnpm run and pnpm exec put its cargo and rustc on the PATH.
  • pnpm add -g rust@<channel> installs a toolchain globally. The cargo and rustc commands run it outside projects that pin their own. pnpm update -g, pnpm ls -g, and pnpm remove -g manage it like any global package.
  • In a project, pnpm add rust@<channel> pins the toolchain in rust-toolchain.toml.
  • pnpm shim add rust adds project-aware shims for cargo, rustc, and the other Rust tools. In a project with a rust-toolchain.toml, they run the toolchain the file names and install it on first use. Elsewhere, the next command of the same name on PATH runs, such as rustup's.

• pnpm run and pnpm exec now keep the colors of script output that they print under the project's name, such as with --stream. pnpm sets FORCE_COLOR=1 for these scripts when its own output is in color, unless FORCE_COLOR is already set.

  Script output is also rendered more cleanly:

  • A line that a progress bar redraws with \r shows only its last state.
  • Escape codes that move the cursor or clear the screen are dropped.
  • Long colored lines are cut at the terminal width.
  • pnpm -r run no longer garbles its live output when a script fails while other scripts are still running.

Patch Changes

Installing packages

• pnpm no longer panics with "unexpected error when polling the I/O driver" when it runs under QEMU user-mode emulation, such as a linux/amd64 container on an Apple Silicon Mac #​16696.

• pnpm view, pnpm update, and other commands that read registry metadata now work behind proxies that end a response by closing the connection without a TLS close_notify alert #​16704.

• pnpm now switches to the version a project pins in packageManager or devEngines.packageManager even when pnpm-workspace.yaml has a setting the running pnpm cannot read, such as a lockfile.includeResolutionSettings section. If pnpm does not switch, it still reports that setting #​16675.

• When the pnpm package has to download its native binary on first run, it now uses the registry and credentials from .npmrc and from the npm_config_registry and pnpm_config_registry environment variables. COREPACK_NPM_REGISTRY still takes precedence. A project .npmrc is not read when COREPACK_INTEGRITY_KEYS turns off the signature check #​16655.

• pnpm install and pnpm add --config now apply minimumReleaseAge when they resolve a config dependency. A config dependency range resolves to the newest version that is old enough, so a later clean pnpm install --frozen-lockfile accepts the lockfile #​16660.

• pnpm remove with catalogPrune no longer removes catalog entries that pnpm-lock.yaml still records for workspace projects missing from disk. Before, a following frozen install failed with ERR_PNPM_LOCKFILE_CONFIG_MISMATCH #​16679.

• With cargo.enabled, pnpm install now writes the source replacement for vendored crates into .pnpm/crates/config.toml and includes it as optional from .cargo/config.toml. A checkout without .pnpm builds with plain Cargo #​16659.

• With nodeLinker.type set to loaded, Node.js now stops with ERR_PNPM_LOADER_UNSUPPORTED_NODE when it preloads the store loader on a version the loader cannot serve. The supported versions are ^24.18.0 || >=26.2.0. On other versions, CommonJS packages imported from ESM failed with Cannot find module on their first relative require().

• On Windows, pnpm install no longer fails with "The filename, directory name, or volume label syntax is incorrect" when a package contains a file whose name is invalid on Windows, such as icon.svg?as=metadata.d.ts. pnpm removes the invalid characters from the name and prints a warning that lists the renamed files.

• On Windows, hoisting no longer fails intermittently with link errors when a junction is created or replaced concurrently pnpm/tasks#53.

Resolving dependencies

• pnpm install --no-optional now installs the peer dependencies a project declares when autoInstallPeers is on. The lockfile marked such a peer optional: true when another dependency had it as an optional peer.

• pnpm install and pnpm dedupe now link an optional peer to the workspace package that the workspace root depends on when the picked version matches it. They installed the registry package with the same name and version #​16706.

• Removal overrides such as "debug>supports-color": "-" now also apply to an optional peer that a package declares only in peerDependenciesMeta #​16681.

• pnpm add and other installs that re-resolve dependencies now keep the locked devEngines.runtime version while it still satisfies the declared range #​16764.

• pnpm audit --fix update now updates only the dependencies whose locked version is vulnerable #​14928.

• pnpm outdated and pnpm update --interactive now apply overrides before they look up the latest version. Before, a dependency overridden to an npm alias was compared with the latest version of the package the override replaces #​16719.

Patched dependencies

• Patches saved with CRLF line endings now apply, including a patch that creates or deletes a file. pnpm rejected the git headers of such a patch with ERR_PNPM_INVALID_PATCH and the message invalid file mode: 100644 #​16641.

• A patch that changes a file's mode, such as adding or removing the executable bit, now applies the new mode on Unix pnpm/tasks#110.

Injected dependencies and deploy

• With sharedWorkspaceLockfile: false, an injected workspace package installed in the same run as its dependent now holds only the files its files field selects. The copy also held other files of the project, such as tsconfig.json #​16683.

• A script listed in syncInjectedDepsAfterScripts no longer fails when it rewrites package.json while pnpm is copying its edits into the injected copies. The sync after the script now replaces a half-copied manifest.

• pnpm deploy with a shared lockfile no longer fails with ERR_PNPM_LOCKFILE_CONFIG_MISMATCH for settings.dedupeInjectedDeps or settings.dedupePeerDependents when lockfile.includeResolutionSettings is enabled. The deployed lockfile now records both settings as false, the values the deploy installs with.

• pnpm deploy now writes the dependencies in the deployed package.json sorted by name. It also sorts the allowBuilds entries in the deployed pnpm-workspace.yaml. Repeated deploys of the same lockfile now produce identical files #​16687.

Packing and publishing

• pnpm pack and pnpm publish now match .npmignore and .gitignore rules the way npm does. A negation such as !lib/** or !lib/**/!(*.map) re-includes files under a directory that an earlier * rule excluded #​16743.

• pnpm pack and pnpm publish no longer always include root files that merely start with README, LICENSE, or LICENCE, such as README_INTERNAL.md. Only README, LICENSE, LICENCE, and COPYING, with or without an extension, ship regardless of files and .npmignore, as in npm #​16753.

• pnpm publish --provenance=false and --no-provenance now turn off provenance under trusted publishing, so a package can be published from a self-hosted runner. Setting provenance: false in pnpm-workspace.yaml does the same #​16721.

Speed and resource use

• pnpm install hardlinks files from a group-writable or world-writable store again. pnpm copied every file from such a store into node_modules #​16677.

• A repeat pnpm install no longer imports patched packages and packages with build scripts again when nothing changed. Their builds no longer run again either. This happened when recursiveInstall was false or the project had a file: dependency #​16705.

• Verifying the lockfile against trustPolicy and minimumReleaseAge uses less memory. pnpm no longer keeps every published version's manifest of each checked package in memory until the install ends #​16656.

• pnpm rebuild <pkg> and pnpm rebuild --pending no longer read the manifest of every installed package to find build scripts. Only the selected packages are inspected and built. On a large node_modules served lazily, such as over a network or FUSE mount, this turned a rebuild of a few packages into a fetch of every package.

• pnpm rebuild no longer removes and recreates node_modules when the settings recorded in node_modules/.modules.yaml differ from the current configuration. The rebuild runs the build scripts against the installed packages as they are.

• pnpm store prune now compacts the store's index.db after removing package entries, so the file shrinks again #​16717.

Registry commands

• pnpm whoami, pnpm bugs, pnpm docs, pnpm repo, pnpm star, pnpm unstar, and pnpm stars now honor the --registry option.

• --registry now takes precedence over a scope's configured registry for scoped packages in pnpm access, pnpm view, pnpm repo, pnpm star, pnpm unstar, pnpm owner, pnpm deprecate, pnpm undeprecate, pnpm unpublish, pnpm dist-tag, pnpm team, and pnpm stage. Without --registry, pnpm access now sends a scoped package or scope to the registry configured for that scope.

• Registry commands now keep the path of a registry URL such as https://example.com/npm/ when they build request URLs. This applies to pnpm access, pnpm owner, pnpm ping, pnpm search, pnpm star, pnpm stars, pnpm team, pnpm unstar, and pnpm whoami.

• pnpm view now honors the network retry settings.

• pnpm repo now fetches the repository URLs of several packages in parallel.

Platinum Sponsors

Gold Sponsors

prettier/prettier (prettier)

v3.9.10

Compare Source

diff

Markdown: Update micromark-extension-gfm-table to fix the table parse issue on performance (#​20266 by @​fisker)

See micromark/micromark-extension-gfm-table@4f43ead for details.

renovatebot/renovate (renovate)

v44.156.1

Compare Source

Bug Fixes

• config: document where file matching options can be used (#​46695) (e79dd16), closes #​43020
• config: document where our automerge and grouping options can be used (#​46692) (415e46b), closes #​43020
• config: document where rate limits can be used (#​46696) (677e621), closes #​43020

v44.156.0

Compare Source

Features

• deps: update renovate-base-image to v13.122.0 (main) (#​47026) (0eb92be)

Miscellaneous Chores

• deps: update dependency astral-sh/uv to v0.13.1 (main) (#​47024) (53b419b)
• deps: update dependency uv to v0.13.1 (main) (#​47025) (1d6dd52)

v44.155.8

Compare Source

Build System

• deps: update dependency cronstrue to v3.30.0 (main) (#​47021) (754c581)

v44.155.7

Compare Source

Miscellaneous Chores

• deps: update dependency katex@>=0.11.0 <0.18.2 to v0.19.0 (main) (#​47018) (5c074fd)
• deps: update dependency shell-quote@>=1.8.4 <1.11.0 to v1.12.0 (main) (#​47019) (7c9f750)

Build System

• deps: update dependency execa to v10.1.0 (main) (#​47016) (bf10afc)
• deps: update opentelemetry-js-contrib monorepo (main) (#​47015) (2985b37)

v44.155.6

Compare Source

Bug Fixes

• deps: override transitive dependencies flagged by pnpm audit (#​46996) (66c56b5)

v44.155.5

Compare Source

Bug Fixes

• http: share concurrent identical cache provider requests (#​46627) (4dc30ea)

v44.155.4

Compare Source

Build System

• deps: update opentelemetry-js monorepo (main) (#​47008) (e6e03fd)

v44.155.3

Compare Source

Bug Fixes

• workers/reconfigure: pass default branch to extraction config (#​46997) (5a3bfc0)

Documentation

• Correct platform feature support table for Dependency Dashboard (#​46777) (109fc99)

v44.155.2

Compare Source

Bug Fixes

• datasource/gitea-tags: return no digest for a missing repo or tag (#​46984) (690da35)
• workers/repository: keep lookup results out of the extract cache (#​46982) (ad515fb)

Miscellaneous Chores

• deps: update dependency pnpm to v11.28.5 (main) (#​46981) (01303d3)
• deps: update dependency vite to v8.3.3 (main) (#​46980) (bc14d80)
• deps: update python docker tag to v3.15.0 (main) (#​46979) (08721b7)

v44.155.1

Compare Source

Bug Fixes

• deps: update renovate-base-image to v13.121.1 (main) (#​46973) (43eb367)

Miscellaneous Chores

• deps: update ghcr.io/containerbase/devcontainer docker tag to v14.32.1 (main) (#​46972) (9947ade)

v44.155.0

Compare Source

Features

• deps: update renovate-base-image to v13.121.0 (main) (#​46971) (b09bb63)

v44.154.1

Compare Source

Bug Fixes

• manager/github-actions: handle digest pinned renovate-image (#​46970) (bbe08af), closes #​46969

v44.154.0

Compare Source

Features

• datasource/rpm: support zstd compressed "primary" files (#​46372) (911b681)

Bug Fixes

• workers/global: apply hostRules and internalHostAccess when resolving globalExtends (#​46666) (cf46a67)

v44.153.1

Compare Source

Bug Fixes

• metadata: strip git+ scheme prefix from source urls for changelog fetching (#​45941) (476456b)
• platform/github: replace rendered alerts after smart truncation (#​45613) (179f69c)

v44.153.0

Compare Source

Features

• manager/apm: scope per-package tags to their own package (#​46737) (7a03427)

v44.152.0

Compare Source

Features

• datasource/devbox: update default registry URL to new search index (#​46853) (33fe146)
• deps: update renovate-base-image to v13.120.0 (main) (#​46953) (7926703)
• monorepo: add google-cloud-rust (#​43978) (f782369)
• preset: add Boto group (#​43760) (d91b82f)
• replacements: add react-native-magic-modal to magic-modal (#​44997) (d30feab)

Bug Fixes

• changelog: preserve dependency-specific embedded notes (#​46733) (8cbd7f5)
• config: document where PR and branch options can be used (#​46690) (9fa0c2e), closes #​43020
• config: document where version lookup options can be used (#​46963) (2e12788), closes #​43020
• config: warn when a top-level repo-only option is used somewhere else (#​46684) (95888e3), closes #​43020
• json-schema: document which options are nullable (#​46687) (2c988ca)
• manager/github-actions: use semver versioning for setup-pixi's pixi-version (#​46864) (77b1572)

Miscellaneous Chores

• deps: update ghcr.io/containerbase/devcontainer docker tag to v14.32.0 (main) (#​46952) (a0af08f)
• deps: update jdx/mise-action action to v5.1.2 (main) (#​46950) (fe98b6b)
• deps: update linters to v1.87.0 (main) (#​46951) ([e4cd0a6](https://redirect.github.com/renovatebot/renovate/commit/e4cd0a6491aac00aacb3e36ce2af8b391

❗ Important

✂ PR body was truncated to here.

[gemini-code-assist]

Code Review

This pull request primarily focuses on upgrading various project dependencies and tools. Key updates include bumping pnpm to version 12.11.2, @types/node to 24.19.2, renovate to 44.155.8, @google/genai to 2.29.1, prettier to 3.9.10, and selenium-webdriver to 4.51.0. Lockfiles and Bazel module files have been updated accordingly to reflect these changes. I have no feedback to provide as there are no review comments and the dependency updates appear correct.

[alan-agius4]

This PR was merged into the repository. The changes were merged into the following branches:

• main: fc3ee91