Update cargo

[weihanglo]

10 commits in 82c3bb79e3a19a5164e33819ef81bfc2c984bc56..39c13e67a5962466cc7253d41bc1099bbcb224c3 2023-02-04 22:52:16 +0000 to 2023-02-12 02:01:08 +0000

• chore: Update to toml v0.6, toml_edit v0.18 (chore: Update to toml v0.6, toml_edit v0.18 cargo#11618)
• doc: more doc comments and intra-doc links (doc: more doc comments and intra-doc links cargo#11703)
• Deny warnings in CI, not locally (Deny warnings in CI, not locally cargo#11699)
• add comment to lto.rs (add comment to lto.rs cargo#11701)
• Re-export cargo_new::NewProjectKind as public (Re-export cargo_new::NewProjectKind as public cargo#11700)
• Add '-C' flag for changing current dir before build (Add '-C' flag for changing current dir before build cargo#10952)
• -Zrustdoc-scrape-example must fail with bad build script (-Zrustdoc-scrape-example must fail with bad build script cargo#11694)
• Update CHANGELOG for 1.68 backports (Update CHANGELOG for 1.68 backports cargo#11690)
• Update 1password to the version 2 CLI (Update 1password to the version 2 CLI cargo#11692)
• chore: autolabel more for A-* (chore: autolabel more for A-* cargo#11679)

r? @ghost

[rustbot]

These commits modify the Cargo.lock file. Random changes to Cargo.lock can be introduced when switching branches and rebasing PRs.
This was probably unintentional and should be reverted before this PR is merged.

If this was intentional then you can ignore this comment.

Some changes occurred in src/tools/cargo

cc @ehuss

[weihanglo]

Oops today is Monday. I suppose to update Cargo on Tuesday but that's fine.

@bors r+ rollup=never p=1

[bors]

📌 Commit 4c4b4c0 has been approved by weihanglo

It is now in the queue for this repository.

[bors]

⌛ Testing commit 4c4b4c0 with merge c3c6d73...

[bors]

☀️ Test successful - checks-actions
Approved by: weihanglo
Pushing c3c6d73 to master...

[rust-timer]

Finished benchmarking commit (c3c6d73): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

Results

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	2.4%	[2.0%, 2.9%]	2
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-	-	0

Cycles

This benchmark run did not return any relevant results for this metric.