Fix version number in releases for 1.95.0

[ehuss]

The incomplete version number prevented the GitHub Release from being generated.

[rustbot]

r? @Mark-Simulacrum

rustbot has assigned @Mark-Simulacrum.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

• Fallback group: @Mark-Simulacrum, @jieyouxu
• @Mark-Simulacrum, @jieyouxu expanded to Mark-Simulacrum, jieyouxu
• Random selection from Mark-Simulacrum, jieyouxu

[Mark-Simulacrum]

@bors r+ rollup p=10

We should also consider adding a tidy lint on this since it's not uncommon for us to get this wrong. Or maybe it can be part of the generated content from relnotes tooling...

[rust-bors]

📌 Commit e27f84a 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 27m 17s
Pushing d227e48 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 18b439f (parent) -> d227e48 (this PR)

Test differences

Show 4 test diffs

4 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 d227e48c560e915fe7c0b8b3e821680a3a0ba739 --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-ext1: 2h 21m -> 1h 42m (-27.7%)
2. x86_64-msvc-ext3: 1h 30m -> 1h 55m (+26.9%)
3. x86_64-gnu-debug: 1h 57m -> 1h 28m (-25.2%)
4. dist-various-1: 1h 16m -> 57m 31s (-24.3%)
5. dist-s390x-linux: 1h 30m -> 1h 12m (-20.5%)
6. dist-x86_64-musl: 1h 45m -> 2h 5m (+18.6%)
7. x86_64-gnu-nopt: 2h 14m -> 2h 37m (+17.0%)
8. dist-aarch64-apple: 1h 52m -> 2h 9m (+15.0%)
9. dist-x86_64-llvm-mingw: 1h 49m -> 1h 33m (-14.7%)
10. aarch64-apple: 2h 54m -> 3h 19m (+14.4%)

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 (d227e48): comparison URL.

Overall result: ✅ improvements - no action needed

@rustbot label: -perf-regression

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-0.1%	[-0.1%, -0.1%]	1
All ❌✅ (primary)	-	-	0

Max RSS (memory usage)

Results (primary 0.5%, secondary 0.9%)

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

	mean	range	count
Regressions ❌ (primary)	2.8%	[2.8%, 2.8%]	1
Regressions ❌ (secondary)	4.0%	[2.2%, 5.2%]	5
Improvements ✅ (primary)	-1.9%	[-1.9%, -1.9%]	1
Improvements ✅ (secondary)	-3.1%	[-3.2%, -3.0%]	4
All ❌✅ (primary)	0.5%	[-1.9%, 2.8%]	2

Cycles

Results (primary 3.3%, secondary 8.6%)

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

	mean	range	count
Regressions ❌ (primary)	3.3%	[3.2%, 3.3%]	2
Regressions ❌ (secondary)	8.6%	[2.7%, 13.3%]	3
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	3.3%	[3.2%, 3.3%]	2

Binary size

This perf run didn't have relevant results for this metric.

Bootstrap: 492.463s -> 492.446s (-0.00%)
Artifact size: 394.15 MiB -> 394.09 MiB (-0.01%)