Skip to content

chore(deps): update proto dependencies bump - #17

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/proto-dependencies-bump
Open

chore(deps): update proto dependencies bump#17
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/proto-dependencies-bump

Conversation

@renovate

@renovate renovate Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Update Change Age Confidence
deno patch 2.9.42.9.5 age confidence
go patch 1.26.51.26.6 age confidence
node (source) minor 26.5.026.7.0 age confidence
pnpm (source) minor 11.17.011.22.0 age confidence
proto minor 0.59.00.60.2 age confidence
python patch 3.14.63.14.7 age confidence
uv minor 0.11.330.12.5 age confidence

Release Notes

denoland/deno (deno)

v2.9.5

Compare Source

  • feat(add): --unscoped flag to alias packages by their unscoped name (#​36319)
  • feat(task): add --members flag to run tasks in workspace members only (#​35748)
  • feat: add Blob/Body textStream() (#​35616)
  • feat: add experimental QuickJS backend (#​36194)
  • fix(bundle): avoid esbuild protocol deadlock (#​36427)
  • fix(bundle): respect runtime file permissions (#​36107)
  • fix(cjs): use loader sources for recursive analysis (#​36111)
  • fix(cli): escape control characters in external metadata (#​36198)
  • fix(core): don't resolve internal module imports with the user's import map
    (#​36303)
  • fix(crypto): add "raw-secret" to KeyFormat type (#​35708)
  • fix(desktop): handle colored HMR URLs and page loads (#​36316)
  • fix(desktop): retain update signature verification op (#​36152)
  • fix(ext/crypto): allow deriveBits with length 0 (#​36283)
  • fix(ext/napi): polyfill uv_handle_size and uv_strerror (#​36308)
  • fix(ext/net): release completed QUIC stream resources (#​36247)
  • fix(ext/net): require --allow-sys for node:dns.getServers() (#​35941)
  • fix(ext/node): Node compat for web streams (#​36285)
  • fix(ext/node): apply backpressure in Readable.toWeb() (#​36321)
  • fix(ext/node): defer TLS write completion callback to avoid reentrancy panic
    (#​35867)
  • fix(ext/node): don't fire http2 settings callback after session destroy
    (#​36230)
  • fix(ext/node): gate constrained memory cgroup reads (#​36218)
  • fix(ext/node): handle pre-quoted shell arguments (#​36371)
  • fix(ext/node): implement node:test tags (#​36292)
  • fix(ext/node): implement util.diff (#​36289)
  • fix(ext/node): implement v8.promiseHooks API (#​36281)
  • fix(ext/node): sort fs.readdir entries to match Node.js (#​36341)
  • fix(ext/node): stop http2 file reads after stream close (#​36300)
  • fix(ext/node): store blocklist ranges compactly (#​36212)
  • fix(ext/node): support the fs flush option for writes (#​36290)
  • fix(ext/node): use signatureAlgorithm digest for X509 ECDSA verify (#​36326)
  • fix(ext/node_crypto): use named group exponent sizes (#​36347)
  • fix(ext/web): attach Node error codes to WHATWG API validation errors (#​36288)
  • fix(ext/websocket): disable HTTP/2 server push on wss upgrade path (#​36327)
  • fix(fetch): scope redirect-sensitive headers by origin (#​36361)
  • fix(ffi): reject resizable buffers in nonblocking calls (#​36259)
  • fix(fmt): accept xml and svg extensions for stdin (#​36149)
  • fix(fmt): update lax-markup to 0.3.2, lax-css and lax-sql to 0.3.0 (#​36397)
  • fix(http): preserve stripped headers across redirects (#​36360)
  • fix(inspector): validate request host headers (#​36348)
  • fix(net): cancel pending writes on stream close (#​36369)
  • fix(net): clean up concurrently dropped load-balanced listeners (#​36246)
  • fix(net): handle malformed DNS record text (#​36374)
  • fix(node): clean up Web Stream finished listeners (#​36227)
  • fix(node): retain consumed HTTP stream wrapper (#​36254)
  • fix(npm): ignore invalid package bin targets (#​36354)
  • fix(npm): tolerate malformed scripts field in packuments (#​36324)
  • fix(npmrc): match auth configs by authority and path (#​36359)
  • fix(outdated): don't report JSR pre-release versions as latest (#​36325)
  • fix(publish): report when the registry rejects a provenance attestation
    (#​36404)
  • fix(resolver): don't treat deno eval modules as npm package files (#​36304)
  • fix(runtime): map notify's Windows missing-path error to NotFound (#​35864)
  • fix(sync-types): add reason to too_many_arguments allows (lint)
  • fix(telemetry): handle reentrant attribute conversion (#​36256)
  • fix(webgpu): own mapped range backing stores (#​36257)
  • fix(webstorage): preserve Storage constructor name (#​35944)
  • fix: capitalize IP in help text (#​36170)
  • fix: upgrade deno_task_shell to 0.33.3 (#​36406)
  • fix: wire no-legacy-abort unstable flag from deno.json config (#​36312)
  • perf(core): run the common-path tick drain in Rust (#​36157)
  • perf(ext/node): bypass dns lookup on literal IPs in udp send (#​35909)
  • perf(ext/web): implement base64url encode/decode as simdutf ops (#​36398)
  • perf(fs): open files on the blocking pool in async readFile/writeFile (#​36160)
  • perf: order startup functions in release builds (#​36219)
  • perf: reduce eager module evaluation at startup (#​36331)
  • perf: remove Linux unwind tables from release artifacts (#​36265)
golang/go (go)

v1.26.6

Compare Source

nodejs/node (node)

v26.7.0: 2026-08-05, Version 26.7.0 (Current), @​aduh95

Compare Source

Notable Changes
  • [58717685a1] - (SEMVER-MINOR) crypto: support loading private keys through STORE loaders (Filip Skokan) #​63949
  • [44b940ee8c] - crypto: update root certificates to NSS 3.125 (Node.js GitHub Bot) #​64746
  • [c1e4f7365e] - (SEMVER-MINOR) lib: add perfetto support (Chengzhong Wu) #​64565
  • [11c2f9c642] - (SEMVER-MINOR) module: implement Symbol.dispose in ModuleHooks (Remco Haszing) #​63928
  • [a646319f61] - (SEMVER-MINOR) test_runner: add support for --test-coverage-include-all (avivkeller) #​64830
Commits
pnpm/pnpm (pnpm)

v11.22.0

Compare Source

v11.21.0: pnpm 11.21

Compare Source

Minor Changes

  • Added interactive group selection to pnpm update --global --interactive.

  • Running pnpm setup, pnpm self-update, or a command that modifies the global installation (such as pnpm add --global) through sudo now prints a warning. pnpm keeps global packages and configuration in the invoking user's home directory, so running these commands as root silently operates on the root user's home directory instead of yours. They will fail with ERR_PNPM_SUDO_NOT_SUPPORTED in pnpm v12. Read-only global commands (such as pnpm bin --global) are unaffected.

Patch Changes

  • Fixed pnpm failing to start under asynchronous Node.js module loaders when no .pnpmfile.mjs exists pnpm/pnpm#11701.

  • Fixed minimumReleaseAge fallback for custom dist-tags so the selected version does not exceed the registry’s original tag target.

  • Removing a dependency from package.json and reinstalling no longer re-resolves the dependency graph. The importer's entry is dropped from pnpm-lock.yaml, anything it made unreachable is pruned, and a catalog entry that loses its last referent is removed — all without registry access. Installs still fall back to a full resolution when a package that stays resolves a peer dependency through the removed one, since that would change the surviving package's entry rather than only prune.

  • Changing a catalog entry to a different exact version no longer re-resolves the dependency graph. The package is replaced in pnpm-lock.yaml directly, reusing the same check the pnpm.overrides fast path applies: every locked dependency of the package must still satisfy the new version's manifest. Installs fall back to a full resolution when anything other than the catalog reaches the package — an importer that depends on it directly, or another package that depends on it — since the graph would then need both versions.

  • Fixed a CI regression where github:owner/repo dependencies (and other shorthand Git specifiers) would fail to install with Permission denied (publickey) on CI runners that lack SSH keys. The Git resolver no longer records an SSH URL unless the user explicitly wrote one (e.g. git+ssh:// or git@host:...):

    • The repository visibility probe (an HTTP HEAD request) now retries transient failures such as 429 Too Many Requests, so host throttling of CI runners is no longer mistaken for a private repository.
    • For non-SSH specifiers, anonymous HTTPS git ls-remote access is now tried before SSH, so a public repository whose visibility probe fails still resolves to a portable HTTPS URL instead of an SSH URL that only works where SSH keys are configured.
    • When every probe fails, the resolver falls back to HTTPS for shorthand and HTTPS-style specifiers, and only guesses SSH when the user explicitly provided an SSH URL.
    • A repository that could not be confirmed public is no longer resolved to the host's anonymous archive URL (e.g. codeload.github.com, which would fail to download for a private repository); it stays a regular git resolution so installs can use ambient Git credentials such as credential helpers and tokens.

    Note that a private repository that is reachable both over authenticated HTTPS and over SSH now resolves to its HTTPS URL, where previous versions recorded the SSH URL.

    Fixes pnpm/pnpm#13276.

  • ng build and nuxt build now work under the global virtual store: pnpm's built-in compatibility extensions add the tslib dependency that @angular/build uses without declaring and the unplugin dependency that @nuxt/vite-builder v4 uses without declaring.

  • Fixed link: dependencies under enableGlobalVirtualStore so linked children are materialized and slots remain isolated by their resolved link targets.

  • An install that skips resolution because pnpm-lock.yaml is already up to date now reacts fully to packages the lockfile removed — for example after pulling a lockfile in which a dependency was deleted. The hoist layer is recomputed, so a package that became hoistable when a direct dependency was removed is hoisted, and pendingBuilds entries for removed packages are dropped instead of staying pending forever.

  • The held-back-update warning printed by pnpm update no longer fires when minimumReleaseAge is the actual reason a newer version was not picked. The warning's baseline now applies the same maturity cutoff as the pick itself, so it no longer wrongly attributes the hold-back to "your manifests and already installed dependencies" or recommends an override that would defeat the age gate. See #​13071.

  • Checking whether ignoredOptionalDependencies is up to date no longer reorders the configured patterns. The check sorted them in place, which could move an ! exclusion ahead of the pattern it excludes from and flip which optional dependencies were ignored.

  • Changing autoInstallPeers, dedupePeers, peersSuffixMaxLength, excludeLinksFromLockfile, or injectWorkspacePackages no longer re-resolves the dependency graph when the lockfile proves the setting cannot affect it: no package or project declares a peer dependency for the peer settings, and no project depends on a directory or on another workspace project for the link and injection settings. The new setting is recorded in pnpm-lock.yaml and the install proceeds from the existing resolution. Every other case still falls back to a full resolution.

  • Adding, editing, or removing an entry in patchedDependencies no longer re-resolves the dependency graph. Resolution never reads a patch — it only records the patch file's hash against the package it matches — so the install now rewrites the affected entries in pnpm-lock.yaml and materializes the patched package from the store instead. Installs still fall back to a full resolution when the patched package is reachable as a peer dependency, and when the new configuration would leave a patch unused while allowUnusedPatches is off, so ERR_PNPM_UNUSED_PATCH is still reported.

  • Resolving a private git repository no longer blocks on an interactive credential prompt: git ls-remote now fails fast with an authentication error when git has no credentials for the repository #​13522.

  • Lockfile verification now honors offline mode by using cached registry metadata instead of reaching the registry. When the required metadata is not available locally, verification reports the same ERR_PNPM_NO_OFFLINE_META condition used by offline resolution.

  • POSIX shell shims now follow symbolic links before computing basedir, preventing execution failures when a shim is invoked via an external symlink on PATH #​13405.

  • The automatic packageManager version switch works again on registries whose tarball URLs point at a different host than the registry itself (load-balanced feed proxies, Artifactory-style mirrors). Package-manager entries are now always recorded with integrity-only resolutions — the download URL is derived from the trusted bootstrap registry instead — and entries persisted in an invalid shape by an earlier pnpm are discarded and re-resolved instead of failing every command #​13619.

  • Registries that serve no npm signature metadata (private mirrors and feed proxies commonly strip dist.signatures) no longer break the automatic packageManager version switch and pnpm self-update #​13147. When the configured registry cannot provide a verifiable signature, pnpm now fetches the signature from registry.npmjs.org and verifies it against the same embedded npm keys over the installed integrity — which proves exactly the same thing. If no signature can be obtained from either source (for example, both are unreachable, or the registry publishes only a shasum), pnpm proceeds with a warning instead of failing, but only when the packages resolve through a registry configured in the user's own (non-project) configuration; the download stays pinned by the lockfile integrity, and a signature that exists but does not validate still fails the switch.

  • pnpm fetch, and any install run with virtualStoreOnly, no longer writes a .pnp.cjs loader under nodeLinker: pnp. These installs populate the virtual store without linking the project, so the loader would have claimed the project resolves out of a store it was never linked into. The importer links and node_modules/.package-map.json were already skipped; the PnP loader now follows the same rule.

  • Prevent pnpm from removing project files when modulesDir resolves to the project root.

  • Speed up installs after adding ignoredOptionalDependencies patterns by removing newly ignored optional dependencies and pruning packages that are no longer reachable without resolving the dependency graph again.

  • When a failed install re-copies a bin script from the store, rerunning pnpm install now reapplies the executable bit to the bin instead of leaving it non-executable #​12742.

  • pnpm root -g and pnpm bin -g now print warnings to stderr instead of stdout, so their stdout stays a clean, machine-readable path. Previously, running either command with --global in a project that pins a package manager (e.g. via the packageManager field) printed a warning like [WARN] Using --global skips the package manager check for this project ahead of the path, breaking programs that capture the output as a path #​13672.

    In pnpm 12, pnpm root -g and pnpm prefix -g are now supported (they previously failed with ERR_PNPM_CLI_ROOT_GLOBAL_UNSUPPORTED / ERR_PNPM_CLI_PREFIX_GLOBAL_UNSUPPORTED), and the reporter output of dlx, create, config, sbom, with, store, prefix, root, and bin goes to stderr, matching pnpm 11.

  • pnpm setup no longer makes Node.js print a MODULE_TYPELESS_PACKAGE_JSON warning about dist/worker.js on every command. The package.json it writes next to a standalone executable now declares "type": "module".

  • pnpm update without saving no longer records a version that the manifest's range excludes. The kept range stays authoritative: a requested version outside it is skipped with a warning, and a requested range, a dist tag, or --latest resolves w

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/proto-dependencies-bump branch from a6554ac to af78ec1 Compare July 29, 2026 15:51
@renovate renovate Bot changed the title chore(deps): update dependency uv to v0.12.0 chore(deps): update proto dependencies bump Jul 29, 2026
@renovate
renovate Bot force-pushed the renovate/proto-dependencies-bump branch 6 times, most recently from 654a4e5 to add218a Compare August 7, 2026 18:03
@renovate
renovate Bot force-pushed the renovate/proto-dependencies-bump branch 6 times, most recently from c10a897 to f068cc8 Compare August 14, 2026 22:47
@renovate
renovate Bot force-pushed the renovate/proto-dependencies-bump branch from f068cc8 to f276336 Compare August 15, 2026 21:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants