Repository navigation
Rust floor (dual track): declare 1.75, pin the lock, enforce in CI - #51
Merged
Merged
Conversation
… it; refresh steering moves to the release procedure)
…dedicated cargo steps
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.
Cargo.toml.in declares rust-version = "1.75" (Ubuntu 24.04's stock rustc); the rusqlite bound stays >=0.25, <0.42. Cargo.lock is regenerated MSRV-aware (format v3; rusqlite 0.31.0, the newest line that builds on 1.75), and a committed .cargo/config.toml keeps future resolutions floor-aware. CI gains a rust-floor job (full build + ctest on stock toolchains) and a ceiling step re-testing the newest allowed rusqlite. Root build.yml replaces .github/workflows/build.yml via the usual rename. Verified on rustc 1.75.0 and stable.