Bump libsqlite3-sys to support version 0.32 as well #221
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
|
The CI errors do not seem to be related to the libsqlite3-sys version bump itself, but to some other dependency updates. |
|
This is due to a dependency of ureq (litemap) having an msrv of 1.81 |
This was referenced Mar 15, 2025
|
@weiznich We've resolved the build error. Please rebase against main so we can merge this. |
This commit increases the maximal supported libsqlite3-sys version to include 0.32 as well. It also fixes a warning about a unknown cfg by just adding it to the allow list as we set that via the build script.
weiznich
force-pushed
the
bump/libsqlite_0.32
branch
from
c8b4ef2 to
7a63020
Compare
urschrei
approved these changes
Mar 17, 2025
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.
This commit increases the maximal supported libsqlite3-sys version to include 0.32 as well. It also fixes a warning about a unknown cfg by just adding it to the allow list as we set that via the build script.
CHANGES.mdorCHANGELOG.md