Add release notes for 1.93.0

[BoxyUwU]

r? @Mark-Simulacrum
cc @rust-lang/release
@rustbot ping relnotes-interest-group

[rustbot]

Hi relnotes-interest-group, this issue/PR could use some help in reviewing /
adjusting release notes. Could you take a look if available? Thanks <3

cc @alex-semenyuk @jieyouxu @joshtriplett @Kobzol @lcnr @traviscross

[Mark-Simulacrum]

@bors r+ squash

[rust-bors]

📌 Commit aa20181 has been approved by Mark-Simulacrum

It is now in the queue for this repository.

[Mark-Simulacrum]

@bors p=5

[rust-bors]

⚠️ A new commit 279f8799e3559f52f84b710f171df3ea680b8634 was pushed to the branch, the PR will need to be re-approved.

[cuviper]

@bors r=Mark-Simulacrum

[rust-bors]

📌 Commit 279f879 has been approved by Mark-Simulacrum

It is now in the queue for this repository.

[rust-bors]

☀️ Test successful - CI
Approved by: Mark-Simulacrum
Duration: 3h 17m 58s
Pushing 058a763 to main...

[github-actions]

What is this?

This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing 63f4513 (parent) -> 058a763 (this PR)

Test differences

Show 3 test diffs

3 doctest diffs were found. These are ignored, as they are noisy.

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 058a763dd295a4ea6a8d0c94e326d852e32f52ea --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

1. x86_64-msvc-2: 8284.1s -> 10422.6s (+25.8%)
2. aarch64-apple: 11262.4s -> 8384.7s (-25.6%)
3. aarch64-gnu-llvm-20-2: 3108.3s -> 2739.4s (-11.9%)
4. dist-ohos-x86_64: 4055.0s -> 4483.6s (+10.6%)
5. test-various: 6834.6s -> 7487.0s (+9.5%)
6. x86_64-gnu-llvm-20-2: 5587.8s -> 6115.9s (+9.5%)
7. dist-riscv64-linux: 4561.3s -> 4968.4s (+8.9%)
8. x86_64-gnu-tools: 3458.1s -> 3751.9s (+8.5%)
9. x86_64-mingw-1: 9644.4s -> 10462.4s (+8.5%)
10. x86_64-mingw-2: 8740.3s -> 9457.8s (+8.2%)

How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

[rust-timer]

Finished benchmarking commit (058a763): 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 (primary -2.0%, secondary 1.5%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

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

Cycles

Results (primary -4.0%, secondary -5.2%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-4.0%	[-8.9%, -0.8%]	23
Improvements ✅ (secondary)	-5.2%	[-13.1%, -2.0%]	14
All ❌✅ (primary)	-4.0%	[-8.9%, -0.8%]	23

Binary size

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

Bootstrap: 474.28s -> 472.185s (-0.44%)
Artifact size: 383.30 MiB -> 383.28 MiB (-0.01%)