updated dependencies in library package

[Makuo12]

Updated some dependencies

All crates in the library package now have the most recent versions of their dependencies.
Also built each crate with the dependency updated to check it works properly.

[rustbot]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Amanieu (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.

[tgross35]

We want to pin these crates in only one place to reduce the number of places that need to be updated when bumping them. So libc should be left as-is, compiler_builtins can be left as-is or turned into only = "0.1". (This applies a few places).

We could probably also use workspace dependencies to make things more clear, but this is probably something that should be brought up on Zulip first since it could affect the ability of the crates to build in different workspaces.

[workingjubilee]

The library is its own workspace now, isn't it?

[tgross35]

Yeah, I was mostly thinking about crates that wind up being part of different workspaces at different times through submodules or symlinks. Miri has some unusual things like that but I do doubt there is anything relevant in library/.

[tgross35]

For the tidy error you'll have to update PERMITTED_STDLIB_DEPENDENCIES in deps.rs since adler has been replaced with adler2.

@rustbot author

[rustbot]

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

[Makuo12]

@tgross35 I have updated adler to adler2 and the tidy check is successful. I want to create a new pull request.

[Makuo12]

@tgross35 the new pull request is at #131577

[Makuo12]

Hey @tgross35
Sorry, I thought I had to because I made new changes, but now I understand what you mean. Should I still try to update dependencies in other crates apart from the library crate?