chore(rust): Update Cargo.lock #2042
Draft
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
|
Want to update this? I agree we should update the lockfile (in fact, maybe we also want that to be one of the Rust CI steps) |
|
I can take a shot at this after the nanoarrow release is cut. What tripped me up when I did this initially is that it introduced a number of clippy lint items and at the time I wasn't able to look into those (but certainly could now). |
|
Ah, hopefully the recent PRs have fixed the Clippy lints |
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.
I keep accidentally updating Cargo.lock because VSCode's rust-analyzer keeps running
cargo update-lockfilewhenever I open the workspace. I figured out how to turn this off; however, it is probably a good idea to update it periodically since it embeds a few references to the current version number. I added a step in the version bumping to do this after a release but I'm also happy to remove that if it will cause problems.