Run cargo update for the root lockfile

[Makuo12]

Update packages to their latest version.

[rustbot]

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 (S-waiting-on-review and S-waiting-on-author) stays updated, invoking these commands when appropriate:

• @rustbot author: the review is finished, PR author should check the comments and take action accordingly
• @rustbot review: the author is ready for a review, this PR will be queued again in the reviewer's queue

[rustbot]

These commits modify the library/Cargo.lock file. Unintentional changes to library/Cargo.lock can be introduced when switching branches and rebasing PRs.

If this was unintentional then you should revert the changes before this PR is merged.
Otherwise, you can ignore this comment.

The list of allowed third-party dependencies may have been modified! You must ensure that any new dependencies have compatible licenses before merging.

cc @davidtwco, @wesleywiser

[rustbot]

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:

$ # rebase
$ git pull --rebase https://github.com/rust-lang/rust.git master
$ git push --force-with-lease

The following commits are merge commits:

• dbc3431

[tgross35]

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.

[bors]

☔ The latest upstream changes (presumably #131869) made this pull request unmergeable. Please resolve the merge conflicts.

[ChrisDenton]

I don't know if this should be closed in favour of the other one or something else so...

r? tgross35

[davidtwco]

License changes look okay, haven't checked the rest

[tgross35]

@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.

[Makuo12]

@tgross35 I am done with the updates.

[rustbot]

rustc_error_messages was changed

cc @davidtwco, @compiler-errors, @TaKO8Ki

These commits modify the Cargo.lock file. Unintentional changes to Cargo.lock can be introduced when switching branches and rebasing PRs.

If this was unintentional then you should revert the changes before this PR is merged.
Otherwise, you can ignore this comment.

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

[bors]

📌 Commit b737d2e has been approved by tgross35

It is now in the queue for this repository.

[klensy]

Title and description need update.

[bors]

⌛ Testing commit b737d2e with merge bfaf118...

[bors]

💔 Test failed - checks-actions

[jieyouxu]

@bors r- (idk maybe someone sync'd?)

[Makuo12]

I am quite unsure why the test failed. Any ideas 🧐?

[clubby789]

cc updates often break things, and this looks like a C compiler related failure. If you revert that part it'll ~probably work

[bors]

☔ The latest upstream changes (presumably #134516) made this pull request unmergeable. Please resolve the merge conflicts.

[rustbot]

Some changes occurred in src/tools/rustfmt

cc @rust-lang/rustfmt

[rustbot]

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:

$ # rebase
$ git pull --rebase https://github.com/rust-lang/rust.git master
$ git push --force-with-lease

The following commits are merge commits:

• 2e05a1c

[rust-log-analyzer]

The job x86_64-gnu-llvm-18 failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)

#21 exporting to docker image format
#21 sending tarball 27.0s done
#21 DONE 32.7s
##[endgroup]
Setting extra environment values for docker:  --env ENABLE_GCC_CODEGEN=1 --env GCC_EXEC_PREFIX=/usr/lib/gcc/
[CI_JOB_NAME=x86_64-gnu-llvm-18]
debug: `DISABLE_CI_RUSTC_IF_INCOMPATIBLE` configured.
---
sccache: Starting the server...
##[group]Configure the build
configure: processing command line
configure: 
configure: build.configure-args := ['--build=x86_64-unknown-linux-gnu', '--llvm-root=/usr/lib/llvm-18', '--enable-llvm-link-shared', '--set', 'rust.randomize-layout=true', '--set', 'rust.thin-lto-import-instr-limit=10', '--enable-verbose-configure', '--enable-sccache', '--disable-manage-submodules', '--enable-locked-deps', '--enable-cargo-native-static', '--set', 'rust.codegen-units-std=1', '--set', 'dist.compression-profile=balanced', '--dist-compression-formats=xz', '--set', 'rust.lld=false', '--disable-dist-src', '--release-channel=nightly', '--enable-debug-assertions', '--enable-overflow-checks', '--enable-llvm-assertions', '--set', 'rust.verify-llvm-ir', '--set', 'rust.codegen-backends=llvm,cranelift,gcc', '--set', 'llvm.static-libstdcpp', '--enable-new-symbol-mangling']
configure: target.x86_64-unknown-linux-gnu.llvm-config := /usr/lib/llvm-18/bin/llvm-config
configure: llvm.link-shared     := True
configure: rust.randomize-layout := True
configure: rust.thin-lto-import-instr-limit := 10

[clubby789]

Changes to rustfmt should be made in the repo.

[ytmimi]

Please revert the rustfmt changes and open up a new PR in https://github.com/rust-lang/rustfmt

[Makuo12]

Okay, I would do that

[tgross35]

For the record, there are easier ways to get involved with rust development than updating a finicky lockfiles :) keep an eye out for E-easy or E-help-wanted issues, or find documentation that you think could be improved. Or stop by on Zulip if there is something specific you might be interested in working on https://rust-lang.zulipchat.com/.

[Makuo12]

@tgross35 thank you. Would look at those then