Repository navigation
build: move to Rust 1.99.1 - #38
Merged
Merged
Conversation
The FerroHEALTH family builds with the latest stable toolchain and declares the release before it as its MSRV, which here stays at 1.98. rust-toolchain.toml and docs/VERSIONS.md move to 1.99.1. Clippy 1.99's new assert_is_empty lint is answered in the tests it names with assert_eq! and assert_ne!, which show the value on failure; no packaged file changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed and why
The FerroHEALTH family builds with the latest stable toolchain, Rust 1.99.1 (released 2026-10-15), and declares the release before it as its MSRV (owner decision 2026-10-21). This workspace already declares
rust-version = "1.98", so only the toolchain moves.rust-toolchain.tomland thedocs/VERSIONS.mdrow move from 1.98.1 to 1.99.1.assert_is_emptylint. Its seven sites, all undertests/, now useassert_eq!orassert_ne!against an empty value of the same type, so a failure prints the value. No file a published crate packages changes, so neither crate version moves.Licensing of contributions
Checklist
cargo fmt --all --check,cargo clippy --workspace --all-targets -- -D warningswith and without--all-featuresand for every feature set of the CI matrix,cargo nextest run --workspace --lockedwith and without--all-features, the doctests,cargo docwithRUSTDOCFLAGS=-D warnings;versions.sh,comment-style.shandcrate-version-guard.shpass.CHANGELOG.mdhas an[Unreleased]entry.