Three things have kept CI red since 2026-10-18; none touches the shipped program.
- **cargo audit** (required on every PR, and the daily Security scan) fails on
RUSTSEC-2026-0370/0371/0372: zvariant, zbus_names and zvariant_derive were folded into
zbus 6 on 2026-10-16 and marked unmaintained the same day. zbus reaches the tree only
through tauri-plugin-opener and tauri-plugin-single-instance, for D-Bus on Linux;
`cargo tree -i zbus --target x86_64-pc-windows-msvc` prints nothing. Every release of both
plugins, the 3.0 alphas included, still requires zbus ^5.9, so there is no update to take.
Ignored individually in .cargo/audit.toml with that reason and a removal condition.
`cargo audit --deny warnings` is clean locally.
- **The Monday fixture-drift job** failed on pip/build-backend-failure/stdout.txt: pip 26
ends a finished bar with the bare elapsed time, not `eta 0:00:00`, so `_is_progress` let
the transfer rate through (15.1 MB/s committed, 75.1 MB/s on the next runner). The rule now
keys on a trailing time token. Old vs new over every committed fixture line: exactly this
one line changes verdict. The fixture is restored to `<PROGRESS>` in binary mode, 7 CRLF
before and after; its blob is again b349d1f, the pre-pip-26 bytes.
- **rfd**: Dependabot's 0.17.2 bump (#83) adds a second rfd to the binary, because
tauri-plugin-dialog 2.8.3 requires ^0.16 and src-tauri depends on rfd only because the
plugin already compiles it. dependabot.yml now ignores rfd >= 0.17 until the plugin moves.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
108 lines
3.9 KiB
YAML
108 lines
3.9 KiB
YAML
# Dependency updates — docs/RELEASE-CI.md §2.
|
|
#
|
|
# Dependabot, not Renovate: there is no Renovate configuration anywhere in the poli0981/.github
|
|
# ops repo, and that repo ships a dependabot-summary.yml, which makes Dependabot the portfolio
|
|
# standard.
|
|
#
|
|
# 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.
|
|
#
|
|
# 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 (the comment on
|
|
# the dependency says so). tauri-plugin-dialog 2.8.3 requires rfd ^0.16, so a 0.17 bump adds
|
|
# a second rfd to the Windows binary instead of updating the one there. Remove once
|
|
# tauri-plugin-dialog moves to 0.17, and bump both together.
|
|
- dependency-name: rfd
|
|
versions: ['>=0.17.0']
|
|
groups:
|
|
# First, so a Tauri crate never lands in the catch-all group below.
|
|
tauri:
|
|
patterns: ['tauri', 'tauri-*']
|
|
cargo-minor-patch:
|
|
update-types: [minor, patch]
|
|
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/*']
|
|
npm-minor-patch:
|
|
update-types: [minor, patch]
|
|
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]
|