Don't pin to exact rusqlite version #120
Merged
+4
−4
Conversation
This file contains 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
cljoly
approved these changes
Dec 9, 2023
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.
Pinning the dependency to the exact version
0.30.0is unnecessary because Cargo doesn't consider 0.30 and 0.31 compatible (Cargo's modified semver considers the first non-zero component of the version as the "major" number that determines compatibility). In addition, pinning to an exact version can prevent an update to an in-theory-compatible 0.30.1 and even cause unresolvable dependency conflicts in downstream packages. To be fair however, rusqlite doesn't seem to use the patch component of the version number anyway so this wouldn't happen in practice.