Files
poli0981andClaude Fable 5.2 8a76e98eea 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>
2026-11-10 05:51:26 +07:00

140 lines
4.9 KiB
YAML

# Dependabot configuration.
#
# Three ecosystems: npm (the app), cargo (the Tauri shell), and github-actions
# (the workflows). Security updates are on repo-wide by default; the entries
# below add scheduled VERSION updates so the tree does not silently rot between
# advisories, and carry the ignore rules that keep unfixable alerts quiet.
#
# `cooldown` holds version updates back for a week after a release is
# published. Most npm supply-chain compromises are caught and yanked within
# that window; security updates ignore the cooldown and still arrive at once.
#
# Why the cargo ignore: `glib` is a transitive dependency of tauri's Linux
# stack, and its security fix requires a semver-major bump the tree does not
# allow, so every Dependabot security-update job for it fails with
# `security_update_not_possible`:
#
# glib 0.18.5 (fix: 0.20.0) pinned by
# tauri's gtk-rs 0.18 Linux stack (gtk/gdk/gio 0.18 require glib 0.18)
#
# Remove the ignore once tauri moves to gtk-rs >= 0.20. (`rand` 0.7.3, the
# other long-standing one, left the tree in v1.0.0 when tauri 2.12 dropped
# kuchikiki.)
#
# 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`, 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
# the `tauri` npm group arrives, run `cargo update -p tauri` (and the plugin
# crates) in src-tauri/ on the same branch — `npm run check:tauri` in CI says
# which ones.
version: 2
updates:
- package-ecosystem: "npm"
directory: "/"
schedule:
interval: "weekly"
cooldown:
default-days: 7
open-pull-requests-limit: 5
commit-message:
prefix: "chore(deps)"
prefix-development: "chore(deps-dev)"
groups:
# One PR per family instead of one per package. A split React or
# typescript-eslint bump is never independently mergeable anyway, and
# CI has to run for each PR. A package joins the FIRST group it matches,
# so the specific families come before the catch-alls.
react:
patterns: ["react", "react-dom", "@types/react", "@types/react-dom"]
i18n:
patterns: ["i18next*", "react-i18next"]
tauri:
patterns: ["@tauri-apps/*"]
ui:
patterns:
[
"radix-ui",
"@radix-ui/*",
"motion",
"cmdk",
"sonner",
"lucide-react",
"clsx",
"@fontsource*",
"react-router*",
"zustand",
]
cloudflare:
patterns: ["wrangler", "@cloudflare/*"]
# TypeScript 7 (`tsc`) and the TypeScript 6 API that typescript-eslint
# still needs, installed side by side as npm aliases (see package.json).
# Dependabot may not resolve `npm:` aliases — if no PR shows up for a new
# 7.x, bump both by hand.
typescript:
patterns: ["typescript", "@typescript/*"]
lint-and-format:
patterns: ["eslint*", "@eslint/*", "typescript-eslint", "prettier*", "knip"]
build-tooling:
patterns:
[
"vite",
"vitest",
"@vitest/*",
"@vitejs/*",
"tailwindcss",
"@tailwindcss/*",
"postcss",
"autoprefixer",
"tsx",
"marked",
"@resvg/*",
]
testing:
patterns: ["@testing-library/*"]
types:
patterns: ["@types/*"]
ignore:
# Majors land in their own planned release because each one needs a real
# migration (Vitest 5 is the current example). Dependabot handles minor +
# 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"
schedule:
interval: "weekly"
# No version-update PRs; this entry only feeds ignore rules to security
# updates. The Rust side moves with tauri (see the note at the top).
open-pull-requests-limit: 0
cooldown:
default-days: 7
ignore:
- dependency-name: "glib"
- package-ecosystem: "github-actions"
directory: "/"
schedule:
interval: "weekly"
cooldown:
default-days: 7
open-pull-requests-limit: 3
commit-message:
prefix: "ci"
groups:
actions:
patterns: ["*"]