relnotes for 1.96#156932
Conversation
|
@rustbot ping relnotes-interest-group |
|
Hi relnotes-interest-group, this issue/PR could use some help in reviewing / cc @alex-semenyuk @jieyouxu @joshtriplett @lcnr @traviscross |
| Cargo | ||
| ----- | ||
| - [Allow a dependency to specify both a git repository and an alternate registry.](https://github.com/rust-lang/cargo/pull/16810/) Just like with crates.io, the git repository will be used locally, but the registry version will be used when published. | ||
| - [Added `target.'cfg(..)'.rustdocflags` support in configuration.](https://github.com/rust-lang/cargo/pull/16846) |
There was a problem hiding this comment.
These fixes aren't there yet, but I'll be adding them by a submodule update in the stable PR:
| - [Added `target.'cfg(..)'.rustdocflags` support in configuration.](https://github.com/rust-lang/cargo/pull/16846) | |
| - [Added `target.'cfg(..)'.rustdocflags` support in configuration.](https://github.com/rust-lang/cargo/pull/16846) | |
| - Fixed [CVE-2026-5222](https://blog.rust-lang.org/2026/05/25/cve-2026-5222/) and [CVE-2026-5223](https://blog.rust-lang.org/2026/05/25/cve-2026-5223/). |
|
FYI, I've added this to stable #156937 (including my suggestion for CVEs) so we can get the pre-release test build going, but I'll wait here on main longer so the interest group has a chance to review. |
This copies every change from `main` and #156932.
|
|
||
| Rustdoc | ||
| ----- | ||
| - [Deprecation notes are now rendered like any other documentation](https://github.com/rust-lang/rust/pull/149931). Previously they used the css `white-space: pre-wrap;` property and stripped any `<p>` elements from the rendered html, however this caused issues and unintuitive behavior. The new behavior should be more predictable, however some multi-line deprecation notes will now be rendered as as single lines. If this is undesirable, you can use the standard markdown method of forcing a linebreak, which is `" \n"` (two spaces followed by a newline). |
There was a problem hiding this comment.
It was pointed out in the forum that this " \n" is itself wrapping lines when rendered, which seems a little ironic. :)
Maybe we don't need to demonstrate the spaces? Something like:
| - [Deprecation notes are now rendered like any other documentation](https://github.com/rust-lang/rust/pull/149931). Previously they used the css `white-space: pre-wrap;` property and stripped any `<p>` elements from the rendered html, however this caused issues and unintuitive behavior. The new behavior should be more predictable, however some multi-line deprecation notes will now be rendered as as single lines. If this is undesirable, you can use the standard markdown method of forcing a linebreak, which is `" \n"` (two spaces followed by a newline). | |
| - [Deprecation notes are now rendered like any other documentation](https://github.com/rust-lang/rust/pull/149931). Previously they used the css `white-space: pre-wrap;` property and stripped any `<p>` elements from the rendered html, however this caused issues and unintuitive behavior. The new behavior should be more predictable, however some multi-line deprecation notes will now be rendered as as single lines. If this is undesirable, you can use the standard markdown method of forcing a linebreak, which is two spaces followed by a newline (`"\n"`). |
| - [Fix layout of `#[repr(Int)]` enums in some edge cases involving fields of uninhabited zero-sized types](https://github.com/rust-lang/rust/pull/146989) | ||
| - [Prevent unsize-coercing into `Pin<Foo>` where `Foo` doesn't implement `Deref`. Some such coercions were previously allowed, but produce a type with no useful public API.](https://github.com/rust-lang/rust/pull/149218) | ||
| - [rustc: Stop passing `--allow-undefined` on wasm targets](https://github.com/rust-lang/rust/pull/149868) | ||
| - [Gate the accidentally stabilized #![reexport_test_harness_main] attribute](https://github.com/rust-lang/rust/pull/152210) |
There was a problem hiding this comment.
| - [Gate the accidentally stabilized #![reexport_test_harness_main] attribute](https://github.com/rust-lang/rust/pull/152210) | |
| - [Gate the accidentally stabilized `#![reexport_test_harness_main]` attribute](https://github.com/rust-lang/rust/pull/152210) |
| tools. | ||
|
|
||
| - [JSON targets: `aarch64` softfloat targets now have to have `rustc_abi` set to `"softfloat"`](https://github.com/rust-lang/rust/pull/152941) | ||
| - [target specs: stricter checks for LLVM ABI values, and correlate that with cfg(target_abi)](https://github.com/rust-lang/rust/pull/153769) |
There was a problem hiding this comment.
| - [target specs: stricter checks for LLVM ABI values, and correlate that with cfg(target_abi)](https://github.com/rust-lang/rust/pull/153769) | |
| - [target specs: stricter checks for LLVM ABI values, and correlate that with `cfg(target_abi)`](https://github.com/rust-lang/rust/pull/153769) |
| - [Distributed builds now contain non-split debuginfo for windows-gnu](https://github.com/rust-lang/rust/pull/152870) | ||
| This appears to improve the quality of backtraces. This change has no effect on the defaults for the output of rustc/cargo on these targets. | ||
| - [Check const generic arguments are correctly typed in more positions](https://github.com/rust-lang/rust/pull/152931) | ||
| - [Remove -Csoft-float](https://github.com/rust-lang/rust/pull/152973) |
There was a problem hiding this comment.
| - [Remove -Csoft-float](https://github.com/rust-lang/rust/pull/152973) | |
| - [Remove `-Csoft-float`](https://github.com/rust-lang/rust/pull/152973) |
r? @cuviper
cc @rust-lang/release