chore(deps): fold this week's updates; tauri 2.12.5; hold i18next at 26.6

Folds Dependabot's #242, #243, #244, #246 and #247 into one change.
Each failed the required `check` job the same way (a new version makes
THIRD_PARTY_NOTICES.md stale) and they conflict with each other in
package-lock.json and the notices.

npm, installed with `npm update --before=2026-11-03`, the 7-day
cooldown Dependabot uses:

- i18next 26.5.11 -> 26.6.0, react-i18next 17.1.9 -> 17.1.11,
  i18next-resources-to-backend 1.2.3 -> 1.2.4
- lucide-react 1.64.0 -> 1.66.0, react-router-dom 7.18.4 -> 7.18.5,
  simple-icons 16.35.0 -> 16.36.0
- vite 8.3.4 -> 8.3.5 (rolldown 1.2.16), @vitejs/plugin-react 6.1.2 ->
  6.2.1, tailwindcss 4.3.3 -> 4.3.4, postcss 8.5.32, autoprefixer
  10.6.2, marked 18.1.1 -> 18.1.3
- eslint 10.13.0 -> 10.14.0, typescript-eslint 8.72.1, knip 6.44.1,
  @types/node 26.6.6
- wrangler 4.152.0 -> 4.156.2 (miniflare 5.20261102.0-beta)

i18next stops at 26.6.x (`~26.6.0` plus a Dependabot ignore for
26.7.x): 26.7 adds the debug-mode warnings for the move to v27, about
1.9 KB gzip in the i18n chunk, which takes the initial load from 279.0
to 280.9 KB, over the 280 KB budget, for code the app never runs.

The undici override is gone: miniflare 5.20261102.0-beta depends on
undici 7.30.1 itself (alert #49 stays fixed).

Rust: tauri 2.12.4 -> 2.12.5, tauri-build / -macros / -codegen 2.7.4,
tauri-runtime-wry 2.12.3, wry 0.57.1, tao 0.37.2, tauri-plugin-dialog
2.8.4 (rfd 0.17), tauri-plugin-single-instance 2.5.5. All older than
the cooldown. THIRD_PARTY_NOTICES regenerated.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
poli0981andClaude Fable 5.2 committed 2026-11-10 05:51:26 +07:00
1 parent dfe5f827dd
commit 8a76e98eea
5 files changed
+625 -879

No files matched your search

+11 -9
View File
@@ -21,16 +21,15 @@
# other long-standing one, left the tree in v1.0.0 when tauri 2.12 dropped
# kuchikiki.)
#
# The npm side has the opposite case, a fix Dependabot cannot reach: miniflare
# (under wrangler, dev only) pins `undici` to an exact version, so the security
# job fails with `security_update_not_possible` and `overrides` in package.json
# lifts it instead:
# The npm side holds one package back on purpose: `i18next` stays on 26.6.x
# (`~26.6.0` in package.json). 26.7, the last 26.x minor, adds the debug-mode
# warnings that prepare the move to v27 — about 1.9 KB gzip in the i18n chunk,
# which takes the initial load from 279.0 KB to 280.9 KB, over the 280 KB
# budget (`npm run check:bundle`), for code the app never runs. Remove the
# ignore and the tilde with the planned i18next 27 migration.
#
# undici 7.29.1 (fix: 7.30.1, alert #49) pinned by
# miniflare 5.x (every release up to 5.20261019.2-beta)
#
# Remove the override once a wrangler release brings undici >= 7.30.1 on its
# own (`npm view miniflare@<version> dependencies.undici`).
# (`undici`, overridden in package.json for alert #49 until v1.5.1, needs no
# override any more: miniflare >= 5.20261101 depends on undici 7.30.1 itself.)
#
# Tauri moves in lockstep: the tauri CLI refuses to build when the
# @tauri-apps/* npm packages and the tauri crates differ in major.minor. When
@@ -110,6 +109,9 @@ updates:
# patch.
- dependency-name: "*"
update-types: ["version-update:semver-major"]
# Bundle budget — see the note at the top.
- dependency-name: "i18next"
versions: ["26.7.x"]
- package-ecosystem: "cargo"
directory: "/src-tauri"