Files
pipdock/.github/dependabot.yml
T
poli0981andClaude Opus 5.5 ccae96dbeb chore: move to poli0981org — self-contained CI, Qodana, an npm licence gate, this week's dependencies (#119)
The repository now lives in the poli0981org organization, and this makes it at home there.

- main was red since 2026-11-18: RUSTSEC-2026-0543 (chrono), in Cargo.lock only through serde_with's weak features and compiled into nothing; ignored with its reason and exit condition.
- Supersedes #113–#118 (Rust 1.100.0, rusqlite 0.42.0, Tauri 2.12.6, code-health pins, actions, npm) plus jsdom 31.0.1; minimatch 11 closes GHSA-g3hv-75wg-m249. rfd 0.18 (#112) is held again until tauri-plugin-dialog moves.
- Dependabot's tauri groups never worked (it picks the most specific group); exclude-patterns on the catch-alls fix it.
- CI is self-contained: no workflow calls poli0981/.github; every action is pinned by commit; notify.yml vendors the Discord notifier.
- npm licences: scripts/check-licenses.mjs, deny.toml's allowlist for the npm half. Required, with cargo deny and tauri lockstep — eight required checks.
- Qodana in two parts (Rust, TS/JS), full scans, a triaged Rust baseline, fail on anything new. The Rust container needed its toolchain and CARGO_HOME pointed somewhere writable before it analysed anything.
- SonarQube Cloud analyses into poli0981org_pipdock; every npm ci runs with --ignore-scripts (S6505).
- Every repository URL points at the organization. README's attestation command for 1.4.0/1.5.0 had stopped working; it now says --owner poli0981 --signer-repo poli0981/pipdock.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-21 21:50:41 +07:00

121 lines
4.8 KiB
YAML

# Dependency updates — docs/RELEASE-CI.md §2.
#
# Dependabot, not Renovate: Dependabot was the standard of the owner's ops repo when the CI was
# set up, and it still is across the poli0981org organization.
#
# Weekly grouped PRs per ecosystem, with Code Health's pins kept apart so a tool bump is reviewed
# on its own. Security advisories bypass grouping and schedule — that is Dependabot's default for
# security updates and cannot be configured away here.
#
# **Cooldown**: a release has to be a few days old before it is proposed. Most yanked or
# compromised releases are pulled within that window, and nothing here needs a dependency the day
# it ships.
#
# **Tauri moves in lockstep**: the `tauri` crate and `@tauri-apps/api` must share a minor or the
# app will not start, and Dependabot cannot bump Cargo and npm in one pull request — a
# multi-ecosystem group can, but what it does to the dependencies outside its patterns is not
# documented, and guessing wrong would silently stop every other update. So each ecosystem groups
# its Tauri packages into one PR, and ci-node.yml's `tauri lockstep` job fails either PR until its
# counterpart is merged beside it.
#
# **A group's position decides nothing.** Dependabot gives a dependency to the *most specific*
# group that matches it, and a group with `update-types` counts as more specific than one with
# patterns alone: on 2026-11-21 its log read "Skipping tauri-plugin-dialog for group 'tauri' -
# belongs to more specific group 'cargo-minor-patch'", and every Tauri bump of that week (#116,
# #118) landed in the catch-all groups. This file said the order kept them out. What does is
# `exclude-patterns` on each catch-all, below.
#
# The labels below must exist in the repository, or Dependabot opens its PRs without them.
version: 2
updates:
- package-ecosystem: cargo
directory: /
schedule:
interval: weekly
day: monday
open-pull-requests-limit: 5
cooldown:
default-days: 3
semver-major-days: 14
ignore:
# src-tauri takes rfd only because tauri-plugin-dialog already compiles it, and 2.8.4 — the
# newest — still requires rfd ^0.17, so rfd 0.18 alone (#112) would put a second rfd in the
# binary. Remove this when tauri-plugin-dialog moves to rfd 0.18, and bump both together:
# `cargo tree -i rfd --target all` must still show one rfd. (The same ignore, at 0.17, went
# on 2026-11-04 when its own condition was met.)
- dependency-name: rfd
versions: ['>=0.18.0']
groups:
tauri:
patterns: ['tauri', 'tauri-*']
cargo-minor-patch:
update-types: [minor, patch]
exclude-patterns: ['tauri', 'tauri-*']
labels: [dependencies, rust]
- package-ecosystem: npm
directory: /
schedule:
interval: weekly
day: monday
open-pull-requests-limit: 5
cooldown:
default-days: 3
semver-major-days: 14
ignore:
# typescript-eslint 8.71 peers `typescript >=4.8.4 <6.1.0`, so a 6.1 bump fails `npm ci` with
# ERESOLVE before a single check runs. Remove once typescript-eslint widens its range.
- dependency-name: typescript
versions: ['>=6.1.0']
groups:
tauri:
patterns: ['@tauri-apps/*']
# @vitest/coverage-v8 peers `vitest` at its exact version, so the two must move in one PR —
# majors included, which is why this group names no update-types: a vitest major bumped
# alone fails `npm ci` with ERESOLVE, as the typescript one below would.
vitest:
patterns: ['vitest', '@vitest/*']
npm-minor-patch:
update-types: [minor, patch]
exclude-patterns: ['@tauri-apps/*', 'vitest', '@vitest/*']
labels: [dependencies, frontend]
- package-ecosystem: github-actions
directory: /
schedule:
interval: weekly
day: monday
cooldown:
default-days: 7
groups:
actions:
patterns: ['*']
labels: [dependencies, ci]
# Code Health tool pins (deptry / vulture / ruff / pip-audit), shipped with the app and resolved
# at release time — CODE-HEALTH-SPEC §2. Its own ecosystem, so a bump here is never bundled with
# application dependencies. A bump also needs tools-constraints.txt regenerated (the command is
# in its header); `cargo test` fails until it is.
- package-ecosystem: pip
directory: /tools
schedule:
interval: weekly
day: monday
cooldown:
default-days: 7
groups:
code-health:
patterns: ['*']
labels: [dependencies, code-health]
# rust-toolchain.toml's pinned channel. A toolchain bump brings new clippy lints, which is why
# it gets a PR of its own rather than arriving with a cargo update.
- package-ecosystem: rust-toolchain
directory: /
schedule:
interval: weekly
day: monday
labels: [dependencies, rust]