Repository navigation
Refresh Cargo.lock for v0.10.0 - #57
Merged
Merged
Conversation
Owner
Author
|
Merging red due to now-known errata in the release procedure- will be addressed for next time |
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 lock refresh, generated in a tree tagged v0.10.0 so the lock's root version stamps correctly: the only change is the root package version, 0.10.0-rc.1 to 0.10.0. Under the dual-track ruling the dependency set is unchanged - rusqlite stays at 0.31.0 (the newest line verified on the Ubuntu 24.04 floor toolchain) and libsqlite3-sys at 0.28.0 - while the published bound remains wide and CI's ceiling step exercises the top of the range. Verified locally on rustc 1.75.0: cargo test --release --locked passes. Merging this is the last step before the v0.10.0 tag is pointed at main.