Update dependencies (this should fix CI failures) #48
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
1 participant
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 PR updates the dependencies in Cargo.toml and runs
cargo update. In order to make the update command affect the repository I had to remove the lock file from the gitignore, but I believe that is not a problem given https://doc.rust-lang.org/cargo/faq.html#why-have-cargolock-in-version-control.This fixes the failure of the CI test suite on my fork of the repository.
I don't know why the CI job decided to always choose version 0.22 of
pyo3, but now it correctly chooses version 0.27, which is the versionperoxideneeds to compile.