-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run cargo update
for the root lockfile
#131577
base: master
Are you sure you want to change the base?
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @ChrisDenton (or someone else) some time within the next two weeks. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
These commits modify the If this was unintentional then you should revert the changes before this PR is merged. The list of allowed third-party dependencies may have been modified! You must ensure that any new dependencies have compatible licenses before merging. |
There are merge commits (commits with multiple parents) in your changes. We have a no merge policy so these commits will need to be removed for this pull request to be merged. You can start a rebase with the following commands:
The following commits are merge commits: |
Please see the rest of the review at #131574, it still applies here. I don’t think there is any reason you needed to make a new PR, it's the same branch. |
☔ The latest upstream changes (presumably #131869) made this pull request unmergeable. Please resolve the merge conflicts. |
I don't know if this should be closed in favour of the other one or something else so... r? tgross35 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
License changes look okay, haven't checked the rest
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Makuo12 this still needs the updates at #131574 (comment) if you are still interested in getting this merged. Specifically, anything that currently has an a.b
or a.b.0
version shouldn't be changed to a.b.c
.
This is also pretty outdated so needs an update.
@tgross35 I am done with the updates. |
cc @davidtwco, @compiler-errors, @TaKO8Ki These commits modify the If this was unintentional then you should revert the changes before this PR is merged. The Miri subtree was changed cc @rust-lang/miri Some changes occurred in src/tools/clippy cc @rust-lang/clippy Some changes occurred in compiler/rustc_codegen_cranelift cc @bjorn3 rust-analyzer is developed in its own repository. If possible, consider making this change to rust-lang/rust-analyzer instead. cc @rust-lang/rust-analyzer |
Er hang on, this previously only touched the manifest files in |
You shouldn't change the versions in Cargo.toml files unless they are semver incompatible versions. Updating Cargo.lock using |
@bjorn3 I reverted back and updated it with cargo update. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is just a standard lockfile update and it looks fine.
Looks like thiserror
released a 2.0 at the beginning of November so the lockfile now has both versions. We use 1.0 a few places in-tree https://github.com/search?q=repo%3Arust-lang%2Frust+%2Fthiserror+%3D%2F+lang%3Atoml&type=code, they should be updated at some point so we can drop the old version sooner (@Makuo12 if you're interested then this would be welcome).
@bors r+ |
Title and description need update. |
cargo update
for the root lockfile
Run `cargo update` for the root lockfile Update packages to their latest version.
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
Update packages to their latest version.