Skip to content

build: update all non-major dependencies (main) - #34153

Open
angular-robot wants to merge 1 commit into
angular:mainfrom
angular-robot:ng-renovate/main-all-non-major-dependencies
Open

angular-robot wants to merge 1 commit into
angular:mainfrom
angular-robot:ng-renovate/main-all-non-major-dependencies

Conversation

@angular-robot

@angular-robot angular-robot commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@nginfra/angular-linking>@babel/core (source) 8.1.0 → 8.1.3 age adoption passing confidence
firebase-tools 15.35.0 → 15.37.0 age adoption passing confidence
pnpm (source) 12.18.0 → 12.21.0 age adoption passing confidence
pnpm (source) 11.28.11 → 11.28.13 age adoption passing confidence

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

Release Notes

babel/babel (@​nginfra/angular-linking>@​babel/core)

v8.1.3

Compare Source

👓 Spec Compliance
  • babel-helpers, babel-plugin-transform-optional-chaining, babel-plugin-transform-regenerator, babel-plugin-transform-spread, babel-runtime-corejs3, babel-runtime
🐛 Bug Fix
  • babel-plugin-transform-block-scoping, babel-plugin-transform-explicit-resource-management
  • babel-generator
  • babel-helper-module-transforms, babel-plugin-proposal-import-defer, babel-plugin-transform-modules-amd, babel-plugin-transform-modules-commonjs, babel-plugin-transform-modules-systemjs, babel-plugin-transform-modules-umd
  • babel-plugin-transform-modules-systemjs, babel-plugin-transform-regenerator
  • babel-plugin-transform-modules-systemjs
  • babel-plugin-transform-block-scoping
  • babel-helper-import-to-platform-api, babel-plugin-proposal-bytes-modules, babel-plugin-proposal-text-modules, babel-plugin-transform-json-modules
  • babel-helper-wrap-function, babel-plugin-transform-async-to-generator
  • babel-plugin-transform-spread
  • babel-parser
  • babel-generator, babel-parser, babel-types
  • babel-plugin-transform-regenerator
  • babel-plugin-transform-duplicate-keys
  • babel-plugin-proposal-export-default-from, babel-plugin-transform-export-namespace-from
  • babel-plugin-transform-computed-properties
  • babel-generator, babel-parser
  • babel-plugin-transform-explicit-resource-management
  • babel-core
  • babel-plugin-transform-for-of
  • babel-helper-string-parser, babel-parser
  • babel-plugin-transform-typescript
🏠 Internal

v8.1.2

Compare Source

👓 Spec Compliance
  • babel-parser
  • babel-plugin-transform-regenerator, babel-plugin-transform-runtime
🐛 Bug Fix
  • babel-helper-module-transforms, babel-plugin-transform-dynamic-import, babel-plugin-transform-modules-amd, babel-plugin-transform-modules-commonjs, babel-plugin-transform-modules-umd
  • babel-parser
  • babel-helper-member-expression-to-functions, babel-plugin-transform-classes, babel-plugin-transform-object-super, babel-plugin-transform-private-methods
  • babel-helper-string-parser, babel-parser
  • babel-generator
  • babel-plugin-transform-class-static-block
  • babel-template
  • babel-helper-module-transforms, babel-parser, babel-plugin-transform-modules-commonjs, babel-plugin-transform-react-pure-annotations, babel-plugin-transform-typescript, babel-traverse, babel-types
  • babel-plugin-transform-exponentiation-operator, babel-plugin-transform-logical-assignment-operators
  • babel-plugin-transform-flow-comments
  • babel-plugin-transform-block-scoping, babel-traverse
  • babel-helpers, babel-plugin-transform-async-generator-functions, babel-plugin-transform-regenerator, babel-runtime-corejs3
  • babel-traverse
  • babel-plugin-transform-regenerator
  • babel-helper-module-transforms, babel-plugin-transform-modules-commonjs
🏠 Internal
  • Other
  • babel-core, babel-helper-fixtures, babel-helper-transform-fixture-test-runner, babel-helpers, babel-node, babel-plugin-transform-runtime, babel-register, babel-template, babel-traverse, babel-types
🏃‍♀️ Performance
firebase/firebase-tools (firebase-tools)

v15.37.0

Compare Source

  • Updated @modelcontextprotocol/sdk to 1.32.2, undici to 6.29.1 and proxy-addr to 2.0.8 to resolve critical and high severity security advisories.
  • Added support for the Node.js 26 runtime (Preview) for Cloud Functions. (#​11393)
  • Fixed firebase deploy --dry-run creating a missing Firestore database. A dry run now reports which database a deploy would create, and where. (#​11491)
  • Added an optional filterExpression parameter to the Crashlytics MCP get_report tool to filter reports by custom keys.
  • Fixed 2nd gen functions staying uncallable after their first deploy failed, because later deploys never set the invoker. (#​8984)
  • Updated Pub/Sub emulator to version 0.8.38.
  • Fixed crashlytics:heapdumps commands accepting --app IDs that do not belong to the target Firebase project.
  • Fixed crashlytics:heapdumps:enable bypassing the confirmation prompt without --force in non-interactive environments.
  • Warned when crashlytics:heapdumps:enable reuses an existing Cloud Storage bucket whose location differs from --location instead of silently ignoring the requested location.
  • Fixed crashlytics:heapdumps:status --json omitting heapDumpCollectionEnabled when disabled, removed duplicated default location text in crashlytics:heapdumps:enable --help, and surfaced Cloud Storage API error details when bucket creation fails.
  • Fixed crashlytics:heapdumps:enable printing an invalid Firebase Console Crashlytics URL by linking to /crashlytics/app/android:<packageName>/issues instead of the GMP App ID.
  • Scoped Crashlytics service agent roles/storage.objectCreator access to the dedicated heap dump Cloud Storage bucket and enabled Uniform Bucket-Level Access and enforced Public Access Prevention in crashlytics:heapdumps:enable.
  • Updated the Firebase SQL Connect local toolkit to v3.4.28, which includes the following changes:
    • Fixed a bug where singular lookup queries using server value key expressions (such as id_expr) did not trigger realtime subscription updates or client-side cache tracking when returning null.
    • Declare and export enums selected only inside nested relations in generated JS and Admin Node SDKs.
  • Fixed deploying a 2nd gen scheduled function to a region without Cloud Scheduler: the deploy now fails before creating the function, and functions:delete can remove a function left behind by an earlier deploy. (#​11453)
  • Restricted cross-origin access on the Cloud Functions emulator /backends endpoint to the active Emulator UI origin.

v15.36.0

Compare Source

  • Fixed Hosting commands failing when unable to ensure the Firebase Hosting API is enabled, logging a warning instead. (#​11335)
  • Updated firebase init hosting and firebase init hosting:github to ensure the Firebase Hosting API is enabled during setup.
  • Added an optional filterExpression parameter to the Crashlytics MCP list_events tool to filter by custom keys.
  • Fixed Crashlytics filter validation rejecting web app version names without a build number.
  • Improved Auth emulator startup time by compiling validation schemas lazily. (#​11176)
  • Updated the Firebase SQL Connect local toolkit to v3.4.26, which includes the following changes:
    • Internal improvements and bug fixes.
  • Fixed the emulators startup message showing 127.0.0.1 for the Emulator UI and Hub when they listen on 0.0.0.0; it now also prints the address they listen on. (#​6222)
  • Fixed a race condition across a second boundary during accounts:signUp in the Auth emulator where validSince could exceed auth_time. (#​11413)
  • Added local machine config persistence to appcheck:debugtokens:create, --local support to appcheck:debugtokens:list, and appcheck:debugtokens:prune to clean up stale local debug tokens.
  • Fixed database:import failing with an unhandled promise rejection when a batch write fails.
  • Fixed emulator crashes when a Firestore rules reload or emulator HTTP handler throws.
pnpm/pnpm (pnpm)

v12.21.0: pnpm 12.21

Compare Source

pnpm 12.21.0 lets pnpm store add prepare tarball and git dependencies for offline installs. It also makes repeated installs keep their peer dependency choices and fixes several lockfile.format: v13, nodeLinker: hoisted, and pnpm deploy failures. If a pnpr server refuses a setting, pnpm now resolves locally.

Minor Changes
  • pnpm store add run in a project now prepares downloaded tarballs for every lockfile entry that pins them. Besides registry packages, pnpm install --offline --frozen-lockfile can then install dependencies on a tarball URL and dependencies on a git host such as GitHub whose lockfile entry records an integrity.
Patch Changes
Installs that failed
  • pnpm now reads a lockfile with a mapping key longer than 1,024 characters written as 'key':, without the ? marker. Before, pnpm install and other commands failed on such a lockfile with ERR_PNPM_BROKEN_LOCKFILE.

  • With lockfile.format: v13, pnpm install no longer fails to create or rewrite the lockfile when a package declares many of its dependencies as peers.

  • Fixed pnpm deploy failing with lockfile.format: v13 when injected workspace packages have hashed peer bindings.

  • Frozen installs with v13 lockfiles now accept valid peer dependencies of injected workspace packages that use catalogs.

  • Fixed injected workspace packages that depend on themselves linking to a nonexistent directory.

  • pnpm install with frozenStore enabled no longer fails with ERR_PNPM_FROZEN_STORE_NEEDS_BUILD when nodeLinker is hoisted. pnpm fetch with nodeLinker: hoisted no longer populates global virtual store links or modifies linked agent skills, and it preserves an existing hoisted node_modules directory #​18037.

  • A requirements.txt beside a pyproject.toml that declares [tool.uv.workspace] without a [project] table no longer makes that directory a Python project. pnpm install stopped there with an error when the directory had a .venv that pnpm did not create #​18023.

Peer dependencies
  • Repeated installs no longer change the peer dependency providers that the previous install chose. This covers adding, updating, or removing a dependency, projects that use different ranges of one dependency, dependency cycles, and injected dependencies with autoInstallPeers: false pnpm/tasks#221.

    An unchanged install keeps a valid locked peer provider even when a direct dependency provides another compatible version. Explicit pnpm add and pnpm update requests take precedence over it.

  • Workspace projects that select different versions of a peer provider no longer share one copy of the package that depends on it. This affected peers reached through an aliased dependency or a peer dependency cycle.

  • A removed dependency no longer comes back as a peer provider. Before, a direct dependency removed with autoInstallPeers: false could be restored from an old peer resolution, and a removed one could still supply its old peer context.

  • With nodeLinker: hoisted and autoInstallPeers: false, pnpm install no longer creates duplicate copies of a package whose resolved peers are identical. A package also no longer loads a copy of its dependency that was resolved with different peer versions #​18003.

  • pnpm deploy now binds optional peers declared only in peerDependenciesMeta for linked workspace packages. The deployed manifest and lockfile also retain these peers when filtering dependency groups.

Running scripts
  • Scripts now stop when pnpm's process group is killed while they are starting.

  • Bin shims in the global virtual store no longer include the hoisted modules directory of the project that installed them #​18035.

  • pnpm pipeline now rebuilds local packages and reruns build scripts after it restores a shared Cargo build cache with Cargo 1.100 or newer. Before, a worktree could reuse build-script output from the worktree that created the cache.

pnpr
  • If the pnpr server refuses a setting the install uses, or cannot return the lockfile format pnpm reads, pnpm install and pnpm update print a warning and resolve locally. Cargo and Python resolution also fall back to resolving locally. pnpm now rejects a pnpr resolution of npm dependencies that does not name its lockfile format.

  • pnpm install with pnprServer now limits the size of the server's resolve and lockfile verification responses. An oversized response ends the request with an error.

  • pnpm now displays pnpr error codes and reasons when remote requests fail.

Other commands and settings
  • pnpm setup and the install script now support PowerShell as the login shell on Linux and macOS. They add PNPM_HOME to PATH in profile.ps1 under $XDG_CONFIG_HOME/powershell or ~/.config/powershell #​18026.

  • A lockfileDir setting that points at the default lockfile directory now installs the same way as leaving it unset pnpm/tasks#275.

Platinum Sponsors

Bit OpenAI Notion
CodeRabbit Cloudflare

Gold Sponsors

Sanity Discord Vite
SerpApi Stackblitz Workleap
Nx Latitude Syntax

v12.20.0: pnpm 12.20

Compare Source

pnpm 12.20.0 records the specifiers of local directory dependencies in the experimental v13 lockfile and fixes several nodeLinker: hoisted, peer dependency, and overrides bugs. The bundled node-gyp no longer ships the undici version that security scanners flag. Remote resolution and shared build caches no longer work with pnpr 0.1.0-alpha.19 or older.

Minor Changes
  • With lockfile.format: v13, pnpm install records the dependency specifiers of local directory packages. Frozen installs reject changed specifiers even when the locked versions still satisfy them.
Patch Changes
Upgrading and security
  • Remote resolution, shared build caches, and release notes no longer work with pnpr 0.1.0-alpha.19 or older. pnpm now reads the capabilities a pnpr server advertises under pnpr.protocols. Installs fail when the server does not confirm the requested resolution and verification policies.

  • The node-gyp bundled with pnpm no longer ships undici 6, which security scanners flag for CVE-2026-84947. On Node.js 26, node-gyp downloads through a proxy or with a custom CA file no longer crash with "invalid onError method" #​17941.

Resolving dependencies
  • Version-selector overrides entries such as "ms@^2.0.0": "2.1.1" now apply to dependencies declared with the catalog: protocol when the catalog entry's range matches the selector #​17922.

  • A root overrides entry that points a package at a workspace: path, such as workspace:./packages/foo, now also applies when a registry package depends on that package pnpm/tasks#270.

  • Git dependencies now accept npm's :: separator between fragment parameters, such as github:owner/repo#v1.0.0::path:packages/foo. Before, pnpm read the whole fragment as a branch name and failed to resolve it #​17827.

  • pnpm dedupe now keeps a locked runtime version, from devEngines.runtime or from a dependency's engines.runtime, when the declared range still admits it. pnpm dedupe --check no longer fails each time a newer Node.js release in the range comes out #​17984.

  • With autoInstallPeersFromHighestMatch, conflicting non-semver peer dependencies now remain missing, and identical non-semver peer specifiers are preserved. Preferred registry versions no longer replace local paths or protocol-prefixed specifiers when pnpm installs missing peers pnpm/tasks#272.

Hoisted node linker
  • With nodeLinker: hoisted, a package now keeps its nested copy of a dependency that it resolved at a version other than the top-level one, including a peer dependency its parent supplies. Before, pnpm could remove that copy as a duplicate or give the top-level slot to a peer variant found deeper in the graph. The package then loaded the top-level version.
Lockfile and peer dependency graphs
  • Fixed pnpm install keeping stale peer bindings after dependency changes. Required dependencies no longer remain marked optional when another workspace project removes a shared package pnpm/tasks#221.

  • Repeated installs now keep the same dependency links when packages form cycles with several peer dependency variants pnpm/tasks#221.

  • Fixed writing lockfile.format: v13 for dependency cycles with missing, optional, or transitive peers. Frozen installs also accept unchanged injected packages whose peers use catalogs. With --no-optional, frozen installs reject required catalog children recorded only as optional dependencies pnpm/tasks#221.

  • pnpm deploy preserves an injected workspace package's resolved dependencies when they differ from the workspace project's own dependencies. This also applies to packages with publishConfig.directory pnpm/tasks#221.

Running scripts and runtimes
  • Scripts that pnpm runs in a process group of their own are now ended when pnpm is killed right after starting them. A parallel run that was killed before pnpm registered its scripts left all of them running.

  • When a command name matches no script and pnpm falls back to running it as a command, the install that runs before scripts now runs once. Its errors and warnings print once #​17977.

  • Failed downloads by project-aware global runtime commands now explain which configuration applies. Node.js failures also list the global mirror settings and environment variables to check.

Other commands and settings
  • Fixed pnpm occasionally crashing on the first HTTPS request, mostly on Windows virtual machines under load. pnpm now seeds TLS randomness from the operating system's random number generator pnpm/tasks#239.

  • Fixed pnpm deprecate, pnpm undeprecate, and pnpm unpublish failing with revision conflicts when a registry cache serves stale package metadata.

  • pnpm sbom now reports malformed workspace manifests. Before, it omitted their packages pnpm/tasks#59.

  • Fixed pnpm store status reporting approved builds of git dependencies as modified when the store contains legacy build metadata.

  • pnpm now recognizes Capawesome Cloud and RWX as CI environments.

Platinum Sponsors

Bit OpenAI Notion
CodeRabbit Cloudflare

Gold Sponsors

Sanity Discord Vite
SerpApi Stackblitz Workleap
Nx Latitude Syntax

v12.19.0: pnpm 12.19

Compare Source

pnpm 12.19.0 adds pnpm fund, lets the loaded node linker handle packages that need a build, and adds the projectScopedOptionalPeers setting and an experimental JSON lockfile format. It also includes a security fix: an offline install error no longer prints registry credentials. pnpm now checks the engines and platform fields of every workspace project, and many hoisted-linker and frozen-lockfile bugs are fixed.

Minor Changes
  • Added pnpm fund, which lists the funding URLs declared by the installed dependencies in the same tree npm fund prints. Use --json for the npm fund --json report and --recursive or --filter to report on workspace projects. pnpm fund <pkg> opens the funding URL of an install

[!IMPORTANT]
✂ PR body was truncated to here.

@angular-robot angular-robot added action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project target: automation This PR is targeted to only merge into the branch defined in Github [bot use only] labels Nov 19, 2026
@angular-robot

Copy link
Copy Markdown
Contributor Author

⚠️ 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: pnpm-lock.yaml
Error: ERR_PNPM_UNSUPPORTED_ENGINE

  × Unsupported engine for /tmp/renovate/repos/github/angular/components:
  │ wanted: {"pnpm":"11.28.13"} (current: {"node":"","pnpm":"12.21.0"})


@angular-robot angular-robot added area: build & ci Related the build and CI infrastructure of the project target: automation This PR is targeted to only merge into the branch defined in Github [bot use only] labels Nov 19, 2026
@pullapprove
pullapprove Bot requested review from crisbeto and ok7sai November 19, 2026 06:34
@angular-robot
angular-robot force-pushed the ng-renovate/main-all-non-major-dependencies branch from eca0243 to 9a31c9c Compare November 20, 2026 00:41
See associated pull request for more information.
@angular-robot
angular-robot force-pushed the ng-renovate/main-all-non-major-dependencies branch from 9a31c9c to 7a8cdbb Compare November 21, 2026 18:24

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project target: automation This PR is targeted to only merge into the branch defined in Github [bot use only]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant