chore(deps): update mise

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	Pending	Age	Confidence
deno	tools	patch	2.9.5 → 2.9.6
go	tools	patch	1.27.0 → 1.27.1
pnpm (source)	tools	minor	11.24.0 → 11.25.0	11.26.0
uv	tools	patch	0.12.6 → 0.12.9	0.12.10

---

Release Notes

denoland/deno (deno)

v2.9.6

Compare Source

• feat(compressible): add support for 'text/x-component' content type (#​36450)
• feat(desktop): clipboard api (#​35750)
• feat(desktop): support checked, icon, and tooltip on menu items (#​36649)
• fix(bundle): isolate esbuild downloads from workspace registries (#​36467)
• fix(cache): combine duplicate headers for Vary matching (#​36476)
• fix(cli_parser): remove orphaned sync-types parser
• fix(core): cap adaptive buffer initial allocations (#​36432)
• fix(core): make Unix pipe fd ownership explicit (#​36353)
• fix(core): make user timer waker state thread-safe (#​36495)
• fix(coverage): compare a range against a line in V8's units (#​36613)
• fix(crypto): preserve RSA-OAEP label bytes (#​36441)
• fix(desktop): keep dots in the app name when resolving the runtime library
  (#​36006)
• fix(desktop): keep the macOS bundle signature valid unless an update is
  applied (#​36574)
• fix(desktop): never block the JS thread on the error-report dialog (#​36575)
• fix(desktop): propagate deno.json version and license into packaged installers
  (#​36577)
• fix(desktop): run Vite-based HMR dev servers inside the desktop runtime
  (#​36488)
• fix(desktop): transport binding args and results as DesktopValue so Uint8Array
  survives (#​36573)
• fix(ext/fetch): enforce permissions for proxy transports (#​36217)
• fix(ext/fetch): only retry transport errors on pooled connections (#​36415)
• fix(ext/fetch): raise default HTTP/2 SETTINGS_MAX_HEADER_LIST_SIZE to 256KB
  (#​36558)
• fix(ext/http): keep request body readable after response is sent (#​36629)
• fix(ext/http): route invalid async responses to onError (#​36437)
• fix(ext/napi): don't invoke napi_wrap finalizer twice at teardown (#​36556)
• fix(ext/napi): run JS-calling finalizers safely, NULL string result, and
  Float16Array (#​36572)
• fix(ext/napi): surface OS error and path on addon load failure (#​36630)
• fix(ext/napi): track pending finalizers by identity (#​36551)
• fix(ext/napi): wake the event loop at the next uv_timer deadline (#​36559)
• fix(ext/net): skip unsupported DNS records in ANY queries (#​36650)
• fix(ext/node): accept string ports in dns.lookupService (#​36546)
• fix(ext/node): build the proxied request target with the URL parser (#​36557)
• fix(ext/node): do not resume client TLS sessions unless requested (#​36592)
• fix(ext/node): fix perf_hooks detail.req.url proxied path duplication (#​36407)
• fix(ext/node): handle readv short reads (#​36211)
• fix(ext/node): require sys permission for inspector.open (#​36465)
• fix(ext/node_sqlite): invalidate sessions on database close (#​36633)
• fix(ext/tls): avoid panic for mismatched client certificate and key (#​36457)
• fix(ext/web): clean up abort handlers when listeners are removed (#​36226)
• fix(ext/web): close transfer MessagePort when a transferred readable is
  cancelled (#​36270)
• fix(ext/web): snapshot SharedArrayBuffer input in TextDecoder.decode()
  (#​36611)
• fix(fetch): require an initial multipart boundary (#​36470)
• fix(ffi): validate struct return buffers (#​36373)
• fix(fmt): honor .editorconfig when formatting from stdin (#​36267)
• fix(fs): require write permission for creating opens (#​36497)
• fix(fs): use a private FsFile constructor token (#​36439)
• fix(glob): retain valid gitignore rules after parse errors (#​36478)
• fix(http): preserve keep-alive after reading request body (#​36690)
• fix(http): truncate streaming responses to content length (#​36496)
• fix(lsp): restrict registry completion endpoint schemes (#​36477)
• fix(node): check reads during require resolution (#​36461)
• fix(node): match domain uncaught exception handling (#​36475)
• fix(node): preserve v8 deserializer view offsets (#​36460)
• fix(node): validate Brotli encoder operations (#​36530)
• fix(node): validate raw outgoing HTTP headers (#​36471)
• fix(node/crypto): preserve binary key export passphrases (#​36443)
• fix(node_crypto): apply RFC 7748 scalar decoding for X448 (#​36466)
• fix(node_crypto): size cipher updates by byte length (#​36459)
• fix(node_shim): preserve explicit argument delimiters (#​36435)
• fix(npm): flatten single-resolution peers when building package ids (#​36608)
• fix(npm): match peer fallbacks when checking peer resolution cache (#​36607)
• fix(npm): remove arrayref dependency (#​36653)
• fix(npm): resolve bare npm specifier when latest is too new for min dependency
  age (#​36619)
• fix(npm): use cached abbreviated metadata under --cached-only (#​36526)
• fix(npm): validate tar paths before extraction (#​36468)
• fix(os): serialize process environment updates (#​36074)
• fix(permissions): check resolved IP against import deny list (#​36486)
• fix(process): reject NULs in Windows arguments (#​36436)
• fix(process): validate whitespace-only loader environment values (#​36431)
• fix(publish): authenticate the package existence check so private packages
  work (#​36656)
• fix(publish): memoize publish order depth (#​36215)
• fix(publish): reject invalid JSR package names (#​36474)
• fix(repl): skip regex literals when validating input (#​36375)
• fix(runtime): unregister dropped signal resources (#​36213)
• fix(web): keep MessagePort resource identifiers private (#​36440)
• fix: bugs in primordials related to ObjectCreate and
  ObjectDefineProperties (#​36541)
• fix: prevent threadpool starvation with concurrent file locks (#​32789)
• perf(core): grow the op driver's future arena on demand (#​36678)
• perf(core): uncontended-borrow fast path for AsyncRefCell (#​36679)
• perf(core): use index-based SafeArrayIterator in primordials (#​36543)
• perf(core): zero-copy snapshot rehydration, drop bincode (#​36680)
• perf(ext/web): apply the base64url op design to standard base64 (#​36422)
• perf(ext/websocket): shrink the op_ws_create future (#​36681)

golang/go (go)

v1.27.1

Compare Source

pnpm/pnpm (pnpm)

v11.25.0: pnpm 11.25

Compare Source

Minor Changes

• Added an opt-in proof of concept that lets installs reuse a dependency's build output across machines, by publishing and restoring signed, organization-scoped artifacts through pnpr instead of running the lifecycle scripts locally.

  Configure it with the new remoteSideEffectsCache setting. A workspace names the eligible organization and packages; everything describing the act of signing — publish, keyId, builderId, trustedKeys, privateKey and the provenance fields — is refused in pnpm-workspace.yaml and read from the global config file or the environment instead.

• Added macOS and Windows x64 and arm64 support to remote shared build artifacts pnpm/pnpm#13771.

• Added the audit.ignorePrune setting. When set to true, pnpm audit --fix removes ignored GHSA entries that no longer appear in the audit report.

• Generalized the experimental shared-artifact protocol so candidates and signed payloads identify a discriminated subject. Dependency side effects use package and source-integrity subjects, while workspace tasks use project and task subjects.

  This changes shared-artifact request bodies and signed payloads. A pnpr server and its clients have to be on matching versions.

• pnpm init now pins the latest pnpm version, instead of the version of pnpm that ran the command. A project scaffolded by an outdated pnpm therefore no longer inherits that staleness through its own devEngines.packageManager / packageManager pin #​7490.

  The version is read from the latest tag on the package-manager registries. When that lookup cannot answer — no network, an unreachable or slow registry, offline, or a latest that the minimumReleaseAge / trustPolicy settings reject — pnpm init pins the running version as before, and never fails or hangs on the lookup. A latest that is older than the running pnpm is never pinned either.

• A scope set in a project's pnpm-workspace.yaml is now ignored, with a warning naming where to set it instead. pnpm login records the scope as a @scope:registry route in the machine-global auth.ini, which outranks ~/.npmrc in every project — so a repository-committed file could redirect a scope such as @acme for all of a user's other projects after one routine login. Use --scope, the PNPM_CONFIG_SCOPE environment variable, or the global config file instead #​13557.

• Verified remote build artifacts are persisted in the shared store with their signed origin metadata. Later installs reverify the artifact against current trust, policy, platform, and source before reuse, while invalid remote variants are quarantined per channel (pnpm/pnpm#13771).

• Persist completed recursive tasks so --resume-from skips exactly the work that passed during a matching interrupted or failed pnpm -r run / pnpm -r exec invocation. When no compatible state exists, pnpm retains its graph-based resume behavior.

• Allowed pnpm update --patches to refresh registry revisions through a configured pnpr server while retaining locked package versions.

• Added explicit registry revision selection with <version>+rN and pnpm update --patches for refreshing revision artifacts without changing package versions. Registry-backed lockfile policy checks recognize historical revisions, and pnpr now preserves safe revision histories from upstream registries.

• Workspace install, rebuild, pack, publish, stage, and lifecycle work now starts as soon as its dependencies finish instead of waiting for an unrelated topological group.

• pnpm stage approve now approves several staged packages at once. Run it without a stage id to pick from the staged versions interactively, or pass a list of stage ids. The whole batch is approved with a single one-time password, and pnpm asks for a new one only once the registry stops accepting it. Inside a workspace, the selected packages are approved in dependency order, and a package whose workspace dependency could not be approved is skipped instead of being published against a dependency that never reached the registry.

• Added per-task concurrency limits to workspace task orchestration. Set tasks.<name>.concurrency in pnpm-workspace.yaml to limit how many instances of that task may run across workspace projects at once:

  tasks:
    build:
      concurrency: 2

• Added support for registry replacement tarballs using standard integrity values, explicit revision fields, registry routing from the registries setting, non-redirecting integrity-addressed URLs, canonical safe-integer revision numbers, and pnpr proxying for immutable upstream revision artifacts.

• sideEffectsCache now declares the whole of how a package's build output is reused — whether one is restored, whether one is saved, and the remote tier that shares it between machines:

  sideEffectsCache:
    read: true
    write: true
    remote:
      org: acme
      packages: ['native-addon']

  sideEffectsCache: true, sideEffectsCacheReadonly, remoteSideEffectsCache, and its organization field all keep working. Where a field is set under both spellings the one above wins; where it is set under only one, it is kept.

  Two behaviors change, both bringing this CLI in line with what the Rust one already did: sideEffectsCacheReadonly: true now blocks writing to the cache, and setting it alongside sideEffectsCache: false gives a read-only view rather than switching the cache off entirely. A cache can also be declared write-only now, to populate one the run does not read.

• Workspace task orchestration (pnpm/rfcs#23). pnpm -r run and pnpm -r exec now schedule per task instead of in topological chunks: a task starts as soon as the tasks it depends on have finished, so a project no longer waits for unrelated projects that happen to share its chunk.

  A new tasks section in pnpm-workspace.yaml declares what a task depends on, using the ^ convention:

  tasks:
    build:
      dependsOn: ['^build']
    test:
      dependsOn: ['build']
    lint: {}

  ^name means the named task in each of the project's workspace dependencies; a bare name means the task in the same project; an entry with no dependsOn declares an empty dependency list. A task with no entry behaves as dependsOn: ['^<its own name>'], which is exactly what the previous chunked ordering implied — an unconfigured workspace gets the scheduler improvement and nothing else changes meaning. A project without the script is reported skipped and passes its edges through to its own dependencies, so a scriptless package does not sever a chain.

  Also part of this change:

  • A dependency cycle among the tasks of a run is now an error naming the participating tasks (ERR_PNPM_TASK_CYCLE) instead of silently running in an arbitrary order. Setting ignoreWorkspaceCycles: true downgrades the error to a warning: the cycle's tasks run in an arbitrary order relative to each other.
  • --resume-from now skips exactly the transitive dependencies of the anchor package; work unrelated to the anchor still runs.
  • Under --no-bail, tasks whose dependencies failed are reported as skipped, not failed, and do not add to the exit code.
  • With --bail (the default), the first failure still ends the run at once and nothing new is dispatched — including scripts already queued behind the concurrency limit.
  • pnpm -r run --dry-run <script> prints the task graph that would execute without running anything (including skipping the verifyDepsBeforeRun check); --json emits the tasks and their resolved dependency edges.
  • Output is inherited rather than piped only when at most one script can ever be in flight (--workspace-concurrency=1, or the graph forces the scripts to run one after another).

Patch Changes

• An _auth entry in the global config file no longer decides which registry packages come from when something else says. A registry or registries declared in pnpm-workspace.yaml or the global config now wins over the route inferred from a stored credential, which still applies where nothing else declares one. The pnpm_config__auth environment variable is unchanged: it stays the way to point a CI runner at a mandated proxy, and still overrides what a repository declares.

• Prevent installs through a symlinked node_modules directory from rewriting the target checkout pnpm/pnpm#14286.

• Treat empty scripts selected by a regular expression as missing before running dependent tasks.

• The options type of the fetch command now declares allowBuilds, a setting its handler already forwarded to the installer. Type-level only — what pnpm fetch does is unchanged.

• Filter hidden scripts matched by a regular expression during recursive runs when a visible script also matches.

• Fixed automatically switched pnpm versions forcing all descendant pnpm processes to use the same version pnpm/pnpm#14309.

• Fixed ERR_PNPM_UNUSED_PATCH validation during incremental installs pnpm/pnpm#13692.

• Fixed pnpm deploy --prod failing when an excluded dev dependency was also declared as an optional peer dependency pnpm/pnpm#14302.

• pnpm update -g no longer downgrades a global package. --latest resolves the latest dist-tag, which can point at an older release than the one installed — after pnpm add -g <pkg>@next, for instance #​14270.

  pnpm update -g also no longer changes the pnpm version. pnpm's own global install belongs to pnpm self-update #​14270.

• Copying a built package to its other hoisted locations no longer replaces the destination directory. With nodeLinker: hoisted, that replacement deleted the dependencies nested inside the destination's node_modules, and made concurrent copies of the same build chunk fail with ERR_PNPM_ENOENT: no such file or directory, rename '.../node_modules/_tmp_...' #​12880.

• pnpm update no longer replaces the specifier a project declares for a dependency that is also listed in overrides. A catalog: reference stays a catalog: reference, and a declared range stays as written, instead of being rewritten to the version the override resolved to #​12115.

• pnpm update no longer moves the range a project declares for a dependency that overrides also lists, even when the override repeats that range verbatim. Previously the updated package.json disagreed with the lockfile, so the next pnpm install --frozen-lockfile failed with a specifier mismatch #​14224.

• Make pnpm add --lockfile-only skip dependency linking pnpm/pnpm#14286.

• --production is accepted again as an alias of --prod on install, fetch, prune, update, list, why, and sbom, and the install that verifyDepsBeforeRun reproduces is now spelled with --prod. pnpm run no longer aborts with "unexpected argument '--production' found" after a production-only install #​14147.

• The progress output no longer overwrites the lines above it once it grows taller than the terminal window #​14270.

• Restoring a dependency's build from the remote side-effects cache no longer downloads files the store already holds.

• Forward patchedDependencies hashes and packageExtensions to pnpr so server-side resolution preserves patches and package extensions in the lockfile and installed packages.

• Published the workspace task graph and scheduler as @pnpm/workspace.task-scheduler so other workspace commands can use the same dependency-aware scheduling as recursive run and exec.

• The environment variables for the remote side-effects cache are named for the setting they configure: PNPM_SIDE_EFFECTS_CACHE_REMOTE_KEY_ID, ..._BUILDER_ID, ..._IMAGE_DIGEST, ..._ARCHITECTURE_BASELINE, ..._PRIVATE_KEY, ..._BUILD_ENV, ..._TRUSTED_KEYS and ..._PUBLISH. The PNPM_REMOTE_SIDE_EFFECTS_CACHE_* names keep working, and the new one wins when both are set.

• A devEngines.packageManager range pin on pnpm is now recorded in pnpm-lock.yaml's packageManagerDependencies when the running pnpm already satisfies it, using the running version and keeping the range as the recorded specifier. Previously only an exact pin — or a range resolved on the way through a version switch — reached the lockfile, so a range pin written by hand (or by any tool other than pnpm add / pnpm self-update) left the project without the shared resolution the pin exists to provide.

• Fixed recursive run cleanup on Windows when a lifecycle script fails while another script's process tree is still running.

• The update notification now suggests pnpm self-update when PNPM_HOME manages the pnpm in use, and the standalone install script otherwise — under Corepack, or when another package manager installed pnpm. pnpm self-update under Corepack names the standalone install script too.

• Enforce allowBuilds when a prepared git dependency is reused from the shared store, and use the lockfile's canonical git resolution ID in approval suggestions.

• Topologically sorting workspace projects now runs in linear time, fixing installs and lockfile updates that stalled for seconds on workspaces with thousands of projects forming deep dependency chains #​14149, #​14151.

Platinum Sponsors

Gold Sponsors

astral-sh/uv (uv)

v0.12.9

Compare Source

Released on 2026-09-01.

Python

• Add CPython 3.15.0rc2 (#​21413, #​21415)

Enhancements

• Add --no-locked and --no-frozen to disable lock modes enabled by UV_LOCKED and UV_FROZEN for a single invocation (#​21408)
• Report the exact command-line lock-mode flag in warnings and errors (#​21402)

Performance

• Speed up cold wheel installs by extracting each streaming ZIP archive in a single blocking task and reusing buffers across files (#​21372)

Bug fixes

• Update async_http_range_reader to 0.11.1 to address a potential memory-safety issue when reading metadata ranges from untrusted wheels (#​21401)
• Remove sensitive headers when redirects cross authentication realms, including same-host redirects that change URL schemes (#​21382)
• Redact secrets in signed URLs from retry diagnostics, including nested request errors (#​21381)
• Give --locked, --frozen, --check, and --check-exists precedence over conflicting UV_LOCKED and UV_FROZEN values (#​21396)
• Prevent concurrent uv processes from redundantly extracting the same local or source-built wheel (#​21400)

v0.12.8

Compare Source

Released on 2026-08-31.

Enhancements

• Warn about invalid tool directories and continue upgrading valid tools with uv tool upgrade --all (#​21368)

Preview features

• Deduplicate identical files within and across cached wheels with the content-addressed-cache preview feature (#​21327)
• Reduce allocations while extracting content-addressed wheels by reusing the hashing buffer across files (#​21340)
• Speed up content-addressed cache cleanup on macOS by reading hard-link counts in bulk (#​21344)

Performance

• Prevent concurrent uv processes from downloading and extracting the same remote wheel more than once (#​21379)
• Speed up dependency graph construction from large lockfiles by indexing packages during traversal (#​21373)
• Extend indexed lockfile traversal to exports, dependency trees, audits, and freshness checks (#​21377)
• Speed up warm resolutions by reducing repeated marker interner work (#​21300)

Bug fixes

• Do not trust hashes from direct URLs discovered only in wheel metadata when installing with --require-hashes (#​21348)
• Use a compatible Azure Storage API version for anonymous and authenticated requests, allowing credential retries when public access is disabled (#​21366)
• Redact Azure shared access signature (sig) query parameters from displayed URLs (#​21360)
• Treat projects below one-level workspace member globs as standalone instead of aborting workspace discovery (#​21341)

Other changes

• Update astral-tokio-tar to 0.7.0 and use effective sizes when tracking extracted hard links (#​21346)

v0.12.7

Compare Source

Released on 2026-08-27.

Python

• Replace managed Python installations when upgrading to a newer build of the same version (#​21323)

Enhancements

• Support Linux s390x, ppc64le, and loongarch64 targets for cross-platform dependency resolution (#​21313)
• Retry downloads with configured credentials when Azure Storage denies anonymous access to an endpoint configured via UV_AZURE_ENDPOINT_URL (#​21318)

Preview features

• Use content-based directory hashes to deduplicate extracted wheels in the cache with the content-addressed-cache preview feature (#​19693)

Bug fixes

• Reject source archives with hash mismatches before persisting their extracted contents to the cache (#​21248)

Other changes

• remove pyx specific features (#​21182, #​21183, #​21184, #​21185, #​21186)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 9am on tuesday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled because a matching PR was automerged previously.

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

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

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

---

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