# NOTE: committing this file REPLACES the Dependabot configuration currently # set through repo settings. # # web/worker/ and web/admin/ need no entry of their own: they are built from # web/package.json, which the /web entry below covers. version: 2 updates: # ── Frontend ────────────────────────────────────────────────────────────── - package-ecosystem: npm directory: /web schedule: interval: weekly day: monday open-pull-requests-limit: 10 groups: # Collapses the long tail of transitive advisories (brace-expansion, # fast-uri, nanoid, postcss, browserslist, …) into ONE PR instead of # one per package, which is what produced the current alert backlog. npm-security: applies-to: security-updates patterns: ['*'] npm-minor-patch: applies-to: version-updates update-types: [minor, patch] radix: applies-to: version-updates patterns: ['@radix-ui/*'] tanstack: applies-to: version-updates patterns: ['@tanstack/*'] tauri-js: applies-to: version-updates patterns: ['@tauri-apps/*'] ignore: # Framework majors are migrations with their own staged PRs, not # something to take as an unattended bump (SvelteKit 3 moved its config, # its $lib alias, its param matchers and the PWA wiring; see CLAUDE.md). - dependency-name: '@sveltejs/kit' update-types: [version-update:semver-major] - dependency-name: '@sveltejs/adapter-static' update-types: [version-update:semver-major] - dependency-name: svelte update-types: [version-update:semver-major] - dependency-name: tailwindcss update-types: [version-update:semver-major] # `typescript` must stay 6: svelte-check and `svelte-kit sync` need the # JavaScript API that TypeScript 7 does not have. TypeScript 7 is the # `@typescript/native` alias (npm:typescript@~7.0.x), bumped by hand with # it - Dependabot mishandles `npm:` aliases (dependabot-core #16488). # See CLAUDE.md, docs/plan/16-toolchain-2026.md and, for the day 7.1 # lets TypeScript 6 go, docs/plan/17-typescript-7.1.md. - dependency-name: typescript update-types: [version-update:semver-major] - dependency-name: '@typescript/native' # The type definitions follow the Node the build runs on (web/.node-version, # which every setup-node repeats), not the newest Node. - dependency-name: '@types/node' update-types: [version-update:semver-major] # ── Desktop / Android shell ─────────────────────────────────────────────── - package-ecosystem: cargo directory: /web/src-tauri schedule: interval: weekly day: monday open-pull-requests-limit: 5 groups: cargo-security: applies-to: security-updates patterns: ['*'] cargo-minor-patch: applies-to: version-updates update-types: [minor, patch] # ── Python pipeline ─────────────────────────────────────────────────────── # requirements.txt and requirements-test.txt pin every package, transitive # ones included, with the sha256 of each file; an update must bring the new # hashes too, and CI installs with --require-hashes, so a PR whose hashes # are wrong fails python-tests instead of reaching a data job. - package-ecosystem: pip directory: / schedule: interval: weekly day: monday open-pull-requests-limit: 5 groups: pip-all: patterns: ['*'] # ── GitHub Actions ──────────────────────────────────────────────────────── - package-ecosystem: github-actions directory: / schedule: interval: weekly day: monday open-pull-requests-limit: 5 groups: actions-all: patterns: ['*'] ignore: # Majors of these two are taken by hand, for every workflow at once: the # data jobs that check out, commit and push run only on a schedule, so a # pull request's CI never exercises them. Keep ONE major across all # workflows - the Node 20 ones (checkout v4, setup-python v5) printed a # deprecation warning on every run until 2026-10-26. - dependency-name: actions/checkout update-types: [version-update:semver-major] - dependency-name: actions/setup-python update-types: [version-update:semver-major]