Weekly cargo update

[github-actions]

Automation to keep dependencies in Cargo.lock current.

The following is the output from cargo update:

    Updating autocfg v1.1.0 -> v1.2.0
    Updating chrono v0.4.35 -> v0.4.37
    Updating clap v4.5.3 -> v4.5.4
    Updating clap_derive v4.5.3 -> v4.5.4
    Updating handlebars v5.1.0 -> v5.1.2
    Updating itoa v1.0.10 -> v1.0.11
    Updating memoffset v0.9.0 -> v0.9.1
    Updating openssl-sys v0.9.101 -> v0.9.102
    Updating pin-project-lite v0.2.13 -> v0.2.14
    Updating r-efi v4.3.0 -> v4.4.0
    Updating regex-syntax v0.8.2 -> v0.8.3
    Updating security-framework v2.9.2 -> v2.10.0
    Updating security-framework-sys v2.9.1 -> v2.10.0
    Updating serde_json v1.0.114 -> v1.0.115
    Updating syn v2.0.55 -> v2.0.57
    Updating tokio v1.36.0 -> v1.37.0
note: pass `--verbose` to see 89 unchanged dependencies behind latest

[rustbot]

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

[Mark-Simulacrum]

@bors r+ rollup=iffy

[bors]

📌 Commit c21d689 has been approved by Mark-Simulacrum

It is now in the queue for this repository.

[bors]

⌛ Testing commit c21d689 with merge 2a4e433...

[rust-log-analyzer]

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

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

[TIMING] core::build_steps::tool::ToolBuild { compiler: Compiler { stage: 0, host: x86_64-unknown-linux-gnu }, target: x86_64-unknown-linux-gnu, tool: "tidy", path: "src/tools/tidy", mode: ToolBootstrap, source_type: InTree, extra_features: [], allow_features: "" } -- 16.394
[TIMING] core::build_steps::tool::Tidy { compiler: Compiler { stage: 0, host: x86_64-unknown-linux-gnu }, target: x86_64-unknown-linux-gnu } -- 0.023
fmt check
tidy check
thread 'deps (.)' panicked at src/tools/tidy/src/deps.rs:522:24:
cmd.exec() failed with `cargo metadata` exited with an error: error: failed to select a version for the requirement `r-efi = "^4.1.0"` (locked to 4.3.0)
candidate versions found which didn't match: 4.4.0
location searched: directory source `/checkout/obj/build/tmp/distcheck/vendor` (which is replacing registry `crates-io`)
required by package `uefi_qemu_test v0.0.0 (/checkout/src/ci/docker/host-x86_64/test-various/uefi_qemu_test)`
perhaps a crate was updated and forgotten to be re-vendored?
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'main' panicked at src/tools/tidy/src/main.rs:60:49:
called `Result::unwrap()` on an `Err` value: Any { .. }
Build completed unsuccessfully in 0:01:01
Build completed unsuccessfully in 0:01:01
make: *** [Makefile:49: check] Error 1
  local time: Sun Mar 31 18:32:41 UTC 2024
  network time: Sun, 31 Mar 2024 18:32:41 GMT
##[error]Process completed with exit code 1.
Post job cleanup.

[bors]

💔 Test failed - checks-actions

[clubby789]

Needs a manual bump. Will open a PR myself