ci(deps): Bump dtolnay/rust-toolchain from 1.95 to 1.100 - #1
ci(deps): Bump dtolnay/rust-toolchain from 1.95 to 1.100#1dependabot[bot] wants to merge 2 commits into
Conversation
Two separate red jobs on 98fe9b4, both workflow config rather than code. release.yml's `test` job ran `cargo test --workspace --locked` with no prior build, so mcp_smoke panicked at mcp_smoke.rs:55 with "missing binary target/debug/copycatd". That test spawns the real binaries out of the target dir, which is why ci.yml's build-test job already has a `Build` step ahead of `Test`; release.yml never got the same treatment. Verified it was not a cache flake: rerunning the job failed identically, while ci.yml's build-test passed on the same commit with the same test command, which leaves the missing step as the only difference. The `build` job was gated on `test`, so the v1.0.0 tag shipped nothing. ci.yml's `audit` job failed on "Resource not accessible by integration" when rustsec/audit-check tried to create a check run. The scan itself was clean ("No vulnerabilities were found"); only the reporting call was denied, because the job inherited a read-only token. Granting `checks: write` (and keeping `contents: read` explicit, since naming one permission drops the rest) fixes the report without touching the scan. The 10 informational advisories the scan does report, 8 unmaintained and 2 unsound, are the archived gtk3-rs stack plus proc-macro-error and memmap2. They are non-blocking and deny.toml already covers the policy, so they stay as they are here. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Bumps [dtolnay/rust-toolchain](https://github.com/dtolnay/rust-toolchain) from 1.95 to 1.100. - [Release notes](https://github.com/dtolnay/rust-toolchain/releases) - [Commits](dtolnay/rust-toolchain@1.95...1.100) --- updated-dependencies: - dependency-name: dtolnay/rust-toolchain dependency-version: '1.100' dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
33b6902 to
7e8de1e
Compare
|
Closing: this one should not be taken. The msrv job pins dtolnay/rust-toolchain to the exact |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Two things that were making the dependabot PRs cost more than they return. Volume. Weekly cargo updates with only patch grouped meant a lockfile PR most weeks. Both ecosystems move to monthly, and patch-sweep widens to patch + minor, so a whole month of routine bumps arrives as one PR and only a major gets a branch of its own. The gui and wayland-x11 groups stay: those move as families. Correctness. The msrv job pins dtolnay/rust-toolchain to the exact rust-version in the root Cargo.toml, which dependabot reads as a version to chase (PR #1 offered 1.95 -> 1.100). Taking that bump would leave the job green while testing nothing, so the action is now in an ignore list with the reason written next to it. The MSRV moves by hand, alongside Cargo.toml, when egui moves it. Also fixes the three chunks_exact_to_as_chunks errors in cat_logo's tests. They are new in clippy 1.98, so they never appeared on the last green run of main (14 Aug) and instead surfaced as a failure on the rmcp PR, where they read as the bump's fault. Verified with the eight cat_logo tests and a clean cargo fmt; local clippy is 1.96 and cannot reproduce them. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L4WQKmPwXy8gKaG8Aqp3C9
Bumps dtolnay/rust-toolchain from 1.95 to 1.100.
Commits
fef302ctoolchain: 1.100.0