Update all non-major dependencies (master)

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence	Type	Update	Pending
@types/react-dom (source)	19.2.5 → 19.2.7			devDependencies	patch
@vitejs/plugin-react (source)	6.1.0 → 6.1.1			devDependencies	patch
i18next (source)	26.4.0 → 26.4.2			dependencies	patch
i18next-cli	1.71.3 → 1.73.0			devDependencies	minor	1.73.1
mcr.microsoft.com/playwright	v1.62.1 → v1.63.0			final	minor
pnpm (source)	11.24.0 → 11.25.0				minor	11.26.0
react-i18next	17.0.12 → 17.0.13			dependencies	patch
vite-plugin-dts (source)	5.0.3 → 5.1.0			devDependencies	minor

---

Release Notes

vitejs/vite-plugin-react (@​vitejs/plugin-react)

v6.1.1

Compare Source

Add compiler.logDiagnostics option

Recoverable React Compiler diagnostics are no longer logged by default. Set compiler.logDiagnostics to true to log them through Vite. Fatal diagnostics are always logged and fail the transform.

Respect environment sourcemap option for React Compiler transform when builder.sharedPlugins is enabled (#​1439)

The React Compiler transform was using the top-level sourcemap option instead of the environment sourcemap option. This caused a problem when the experimental builder.sharedPlugins was enabled.

i18next/i18next (i18next)

v26.4.2

Compare Source

• fix: $&, $`, $' and $$ inside a nested value ($t(key)) now stay literal. nest() handed the resolved value straight to String.replace as the replacement argument, so those sequences were read as replacement patterns: $& re-inserted the $t(...) match, $` / $' inserted the text before / after it, and $$ collapsed to $. Through t() the $& case was worse than a wrong string: the nested lookup resets the shared nesting regexp, so the re-inserted $t(...) was matched again on every pass and t() never returned — also under the default escapeValue: true when the value arrives via a variable forwarded through nesting options ($t(key, { "name": "{{name}}" }) with a name containing $&). The value is now $-escaped at the String.replace call, the same guard interpolate() already has, and a non-string value returned by a formatter in the nesting chain ($t(key, myFormat)) is stringified before that. Nested values are still not HTML-escaped (#​854). Thanks @​mahirhir (#​2447).

v26.4.1

Compare Source

• fix(types): the selector-form keyPrefix overload of getFixedT() is now available under enableSelector: 'strict'. Its constraint was gated on true | 'optimize' only, so under 'strict' it collapsed to never, the overload dropped out, and the returned t silently lost its keyPrefix scope (t(($) => $.deep) failed with Property 'deep' does not exist on type '{}'). The same call already typechecked under true and 'optimize'. Thanks @​hovelopin (#​2446).

i18next/i18next-cli (i18next-cli)

v1.73.0

Compare Source

• feat: init runs without the wizard. --yes takes the detected defaults for every question
  not answered by --locales, --input, --output, --backend <local|locize|other> or
  --file-type <ts|js>; --project-id <id> (or LOCIZE_PROJECTID) supplies the Locize project id
  and skips the signup page and the credential prompts. Made for scripts and AI coding agents,
  which cannot drive the prompts.
• feat: init --agent-note (also the last wizard question, default No) appends a short
  ## Internationalization section to AGENTS.md (and CLAUDE.md when present; when neither
  exists, AGENTS.md is created, plus a CLAUDE.md importing it if the project has a .claude/
  folder) so the next agent session knows where the locale files are and how translations are
  managed. The exact text is in the README; --no-agent-note skips the question. Nothing is
  written unless you say yes.
• change: the localize agent prompt (--print-agent-prompt) and the i18next-localization
  skill no longer presume Locize. The agent asks the developer once, before creating the config,
  whether to manage the translations with Locize or keep the files in the repository, and never
  creates a project or asks for an API key unless they chose Locize. The prompt now creates the
  config with init --yes ... instead of the interactive wizard.

v1.72.4

Compare Source

• docs: the README shows the skills.sh install badge for the i18next-localization Agent Skill, and
  i18next-cli --help now ends with a one-line hint on installing it
  (npx skills add i18next/i18next-cli). No other command prints anything new.

v1.72.3

Compare Source

• feat(funnel): the Locize hint after status, extract and sync is now a single line that
  names the untranslated-key gap and the one command that fills it (npx i18next-cli localize),
  each with its own ?from= tagged register link. It only appears when secondary locales
  actually have untranslated keys; the 24h cooldown and the CI/non-TTY suppression are unchanged.

v1.72.2

Compare Source

• fix: extract dynamic keys built from for...of loop variables. for (const unit of UNITS) over
  an as const string array now binds unit while the loop body is walked, just like .map() /
  .forEach() callback parameters already did.
• fix: capture as const arrays of object literals (e.g. [{ unit: 'day' }, { unit: 'hour' }]),
  so both for (const { unit } of UNITS) and UNITS.forEach(({ unit }) => ...) resolve the
  destructured properties.
• fix: resolve object destructuring of a known as const object, e.g. const { unit } = rate;
  followed by t(`msg ${unit}`)
  (#​289).

v1.72.1

Compare Source

• fix: the interactive instrument prompt crashed because it still used inquirer's list prompt
  type, which was removed in inquirer 13; switched to select
  (#​288).

v1.72.0

Compare Source

• feat: locize-sync --changed-only [--base <ref>] syncs and AI-auto-translates only the keys
  that changed on the current git branch vs. the base branch — ideal for translating just a pull
  request's diff instead of the whole project. The source-language files are diffed against the
  merge-base with the base branch (auto-detected via origin/HEAD, main, master, or set with
  --base); key creation, value updates and auto-translation are restricted to those keys, and
  deletions are skipped. Changed keys are scoped per namespace file, and when any plural variant
  of a key changed, all its plural forms are included (target languages often need more CLDR
  plural forms than the source). Also configurable via locize.changedOnly /
  locize.changedOnlyBase. Requires git and locize-cli >= 12.7.
• feat: sync --changed-only [--base <ref>] applies the same branch-diff scoping to the local
  synchronizer: only primary-language keys added or modified on the branch are propagated to the
  secondary language files, and obsolete keys are left in place. Works with JSON, JSON5 and YAML
  translation files (JS/TS resource modules cannot be parsed from git history and fail with a
  clear message). Unusable git setups (git missing, not a repository, unresolvable base ref) fail
  the command with actionable errors that mention actions/checkout fetch-depth: 0 for shallow
  CI clones.

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

i18next/react-i18next (react-i18next)

v17.0.13

Compare Source

• fix(types): the selector-form keyPrefix overload of useTranslation() is now available under enableSelector: 'strict'. useTranslation was gated on true | 'optimize' only, so under 'strict' it resolved to the legacy signature and the selector overload disappeared entirely (keyPrefix: ($) => $.ns.foo failed with Type '($: any) => any' is not assignable to type 'undefined'). Trans already handled all three modes. Companion to the same fix for getFixedT in i18next#2446. Thanks @​hovelopin (#​1930).

qmhc/unplugin-dts (vite-plugin-dts)

v5.1.0

Compare Source

5.0.2 (2026-06-01)

5.0.1 (2026-05-19)

---

Configuration

📅 Schedule: (in timezone Europe/Zurich)

• Branch creation
  • Only on Sunday and Saturday (* * * * 0,6)
• 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]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.