chore(deps): bump rust from 1.89 to 1.95

[dependabot]

Bumps rust from 1.89 to 1.95.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
snapchain-docs	Ready	Preview, Comment	Apr 24, 2026 2:53pm

[github-actions]

Diff Coverage

Diff: origin/main...HEAD, staged and unstaged changes

No lines with coverage information in this diff.

[Copilot]

Pull request overview

This PR updates the Rust toolchain used by the Docker build to a newer Rust release, keeping the containerized build environment current.

Changes:

• Bump the Rust Docker base image from rust:1.89 to rust:1.95.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[manan19]

Rust 1.89 → 1.95 bump analysis

Safety assessment

Likely safe to merge. No MSRV is pinned in Cargo.toml (no rust-version field) and there's no rust-toolchain.toml, so the only places the toolchain is declared are the Dockerfile and .github/workflows/verify-impl.yml. Rust's strong backward-compat guarantees across minor releases mean semantic breakage over 1.90–1.95 is very unlikely; the main realistic risk is new lints firing under CI's RUSTFLAGS="-Dwarnings".

I ran cargo check --all-targets locally with Rust 1.95.0 and the same RUSTFLAGS="-Dwarnings -A mismatched_lifetime_syntaxes" CI uses. Most workspace crates compiled cleanly with zero rustc warnings before the check hit an unrelated local env issue (jemalloc's configure script doesn't like spaces in my checkout path). No new-lint regressions surfaced in the portion that did compile.

Addressed Copilot's comment

Copilot correctly flagged that the Docker image was being bumped to 1.95 while .github/workflows/verify-impl.yml still pinned 1.89.0 — that kind of skew means CI could pass on a version that doesn't match what the Docker build uses. I pushed a commit to this branch bumping CI to 1.95.0 as well so both stay aligned.

Additional observations (not blocking)

• There's a secondary CI gap worth noting separately: .github/workflows/verify.yml's paths-filter for the code label doesn't include Dockerfile, so a pure Dockerfile change wouldn't run the test job. This PR dodges that because it now also touches verify-impl.yml, which is in the filter. Might be worth adding Dockerfile to verify.yml's filter in a follow-up so future Dockerfile-only bumps still exercise the Rust test suite.
• Longer-term, adding a rust-toolchain.toml as the single source of truth (consumed by both the Dockerfile and CI) would prevent this skew from reappearing — the current two-location setup is the kind of thing Dependabot will keep getting half-right.