mirror of
https://github.com/max-sixty/worktrunk.git
synced 2026-11-22 02:53:04 +08:00
Weekly MSRV/toolchain bump to latest stable − 1: Rust 1.99.0 is the
current stable (released 2026-09-28), so `rust-version` in `Cargo.toml`
and `tests/helpers/wt-perf/Cargo.toml` moves `1.97` → `1.98`, and
`rust-toolchain.toml` moves `1.97.0` → `1.98.0`.
Verified locally on 1.98.0: `cargo clippy --all-targets --all-features
-- -D warnings` is clean, and in `cargo run -- hook pre-merge --yes` the
`lockfile`, `pre-commit`, `doctest`, and `doc` steps pass. `insta` ran
5,072 tests with 7 failures, all from the CI sandbox rather than the
toolchain: `AF_UNIX` sockets are blocked (the non-regular-file and
fsmonitor tests), a temp key file gets mode 0644 so `ssh-keygen` refuses
to sign, and PowerShell is installed in the sandbox. The four that ran
before nextest stopped also fail on 1.97.0 at `main`. `cargo msrv
verify` isn't installed here; this PR's `msrv` CI job runs it.
**`flake.lock` needs no change.** The locked `rust-overlay` revision
(`f60c1b57ff805a46b5175c76fc981fb4f81efbcc`, 2026-08-23) already ships
`manifests/stable/1.98.0.nix`, so the dev shell's
`rust-bin.stable.${channel}` lookup resolves 1.98.0 as locked; the
`nix-flake` CI job evaluates it. (`nix flake update rust-overlay` can't
run in the tend sandbox anyway — no access to the nix daemon socket;
max-sixty/tend#1197.)
The `nightly-2026-08-01` pins in `nightly.yaml` are about two months
old, inside the three-month window, so they stay.
Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com>
4 lines
66 B
TOML
4 lines
66 B
TOML
[toolchain]
|
|
channel = "1.98.0"
|
|
components = ["rustfmt", "clippy"]
|