Repository navigation
Advance the rusqlite bound to <0.42 (resolve 0.41.0) - #43
Merged
Merged
Conversation
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.
The release advance-and-test step for rusqlite: 0.41.0 is the current rusqlite release, so the tested ceiling in Cargo.toml.in moves from <0.41 to <0.42, and Cargo.lock is refreshed to resolve rusqlite 0.41.0 (libsqlite3-sys moves 0.38.2 → 0.39.1 with it; nothing else changes).
Verified locally: the crate builds against rusqlite 0.41.0 and its test suite passes through the project's cargo_test harness (4 unit tests + 1 doc test).