Skip to content

error on empty export_name#155515

Merged
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
folkertdev:export-name-not-empty
May 10, 2026
Merged

error on empty export_name#155515
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
folkertdev:export-name-not-empty

Conversation

@folkertdev

Copy link
Copy Markdown
Contributor

fixes #155495

Using an empty string as the name makes LLVM make up a name. However this name can be inconsistent between compilation units, which is UB and can cause linking errors, and some parts of LLVM just crash on the empty name (see the linked issue).

As far as we know there is only one valid pattern that could use this, a #[used] static that is not referenced by the program at all. That is not UB, but the export_name is not required for that to work, just normal rust name mangling would do fine.

Technically this is a breaking change, but it seems unlikely that this actually breaks code in the wild that wasn't already broken. I'll leave it up to T-lang to determine what is required here (crater run, FCW, ...), but my gut feeling is that we could just merge this and nobody would notice.

@folkertdev folkertdev added the I-lang-nominated Nominated for discussion during a lang team meeting. label Apr 19, 2026
@rustbot

rustbot commented Apr 19, 2026

Copy link
Copy Markdown
Collaborator

Some changes occurred in compiler/rustc_attr_parsing

cc @jdonszelmann, @JonathanBrouwer

@rustbot rustbot added A-attributes Area: Attributes (`#[…]`, `#![…]`) S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Apr 19, 2026
@rustbot

rustbot commented Apr 19, 2026

Copy link
Copy Markdown
Collaborator

r? @jdonszelmann

rustbot has assigned @jdonszelmann.
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:

  • Owners of files modified in this PR: compiler
  • compiler expanded to 72 candidates
  • Random selection from 17 candidates

@Urgau

Urgau commented Apr 19, 2026

Copy link
Copy Markdown
Member

Should we consider a symbol name with only white spaces as empty?

@folkertdev

Copy link
Copy Markdown
Contributor Author

Hmm, I don't know that it's useful at all but it apparently does work https://godbolt.org/z/dMqhK6hbx

" ":
.Lfunc_begin0:
        .cfi_startproc
        .file   1 "/app" "example.rs"
        .loc    1 2 16 prologue_end

//~^ ERROR `export_name` may not contain null characters
fn null_terminated() {}

#[export_name = "\0"]

@jdonszelmann jdonszelmann Apr 20, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

did we not already have a test for these? thanks for making one in that case

View changes since the review

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We did test that the error code is emitted in tests/ui/error-codes/E0648.rs, but now that this condition is checked in the parser a parser test seemed appropriate, plus this tests some extra inputs.

@jdonszelmann

Copy link
Copy Markdown
Contributor

r=me on implementation after lang approves this one, technically a breaking change

@jdonszelmann jdonszelmann added S-waiting-on-t-lang Status: Awaiting decision from T-lang and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Apr 20, 2026
@traviscross traviscross added I-lang-radar Items that are on lang's radar and will need eventual work or consideration. P-lang-drag-1 Lang team prioritization drag level 1. https://rust-lang.zulipchat.com/#narrow/channel/410516-t-lang T-lang Relevant to the language team labels Apr 22, 2026
@traviscross

Copy link
Copy Markdown
Contributor

Makes sense to me. Thanks @folkertdev.

@rfcbot fcp merge lang

@jdonszelmann

Copy link
Copy Markdown
Contributor

@folkertdev r=me in 10 days when the fcp runs out :)

@folkertdev

folkertdev commented Apr 23, 2026

Copy link
Copy Markdown
Contributor Author

Yeah, the bot seems kind of stuck though. @traviscross maybe just try again?

edit: it's being looked into #t-infra > rfcbot unresponsive

@traviscross

Copy link
Copy Markdown
Contributor

(The bot has been fixed.)

@rfcbot fcp merge lang

@rust-rfcbot

rust-rfcbot commented Apr 24, 2026

Copy link
Copy Markdown
Collaborator

Team member @traviscross has proposed to merge this. The next step is review by the rest of the tagged team members:

No concerns currently listed.

Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!

cc @rust-lang/lang-advisors: FCP proposed for lang, please feel free to register concerns.
See this document for info about what commands tagged team members can give me.

@rust-rfcbot rust-rfcbot added proposed-final-comment-period Proposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off. disposition-merge This issue / PR is in PFCP or FCP with a disposition to merge it. labels Apr 24, 2026
@scottmcm

Copy link
Copy Markdown
Member

Usual analysis: this is the kind of place where I wonder about making it a lint or a hard error, but here I think hard error is the right choice since

  • It's a simple check that's easy to describe, rather than something nuanced that would plausibly need to change more later
  • Defining the current behaviour of "generate something random" sounds terrible and isn't explained by other things that we need to document anyway, so it would be more work in the spec if it was a lint

@rfcbot reviewed

@rust-rfcbot rust-rfcbot added final-comment-period In the final comment period and will be merged soon unless new substantive objections are raised. and removed proposed-final-comment-period Proposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off. labels Apr 29, 2026
@rust-rfcbot

Copy link
Copy Markdown
Collaborator

🔔 This is now entering its final comment period, as per the review above. 🔔

@traviscross traviscross removed the I-lang-nominated Nominated for discussion during a lang team meeting. label May 6, 2026
@folkertdev folkertdev removed the S-waiting-on-t-lang Status: Awaiting decision from T-lang label May 9, 2026
@folkertdev

folkertdev commented May 9, 2026

Copy link
Copy Markdown
Contributor Author

@bors r=jdonszelmann rollup

@rust-bors

rust-bors Bot commented May 9, 2026

Copy link
Copy Markdown
Contributor

Unknown value for argument "r". Run @bors help to see available commands.

@folkertdev

Copy link
Copy Markdown
Contributor Author

@bors r=jdonszelmann rollup

@rust-bors

rust-bors Bot commented May 9, 2026

Copy link
Copy Markdown
Contributor

📌 Commit d0ea88e has been approved by jdonszelmann

It is now in the queue for this repository.

@rust-bors rust-bors Bot added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label May 9, 2026
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request May 9, 2026
…r=jdonszelmann

error on empty `export_name`

fixes rust-lang#155495

Using an empty string as the name makes LLVM make up a name. However this name can be inconsistent between compilation units, which is UB and can cause linking errors, and some parts of LLVM just crash on the empty name (see the linked issue).

As far as we know there is only one valid pattern that could use this, a `#[used]` static that is not referenced by the program at all. That is not UB, but the `export_name` is not required for that to work, just normal rust name mangling would do fine.

Technically this is a breaking change, but it seems unlikely that this actually breaks code in the wild that wasn't already broken. I'll leave it up to T-lang to determine what is required here (crater run, FCW, ...), but my gut feeling is that we could just merge this and nobody would notice.
rust-bors Bot pushed a commit that referenced this pull request May 9, 2026
Rollup of 5 pull requests

Successful merges:

 - #148214 (Consider `Result<T, Uninhabited>` and `ControlFlow<Uninhabited, T>` to be equivalent to `T` for must use lint)
 - #149362 (Add Command::get_resolved_envs)
 - #155188 (Add regression test for issue 144329)
 - #155515 (error on empty `export_name`)
 - #155817 (validate `#[link_name = "..."]` & `#[link(name = "...")]` parameters)
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request May 9, 2026
…r=jdonszelmann

error on empty `export_name`

fixes rust-lang#155495

Using an empty string as the name makes LLVM make up a name. However this name can be inconsistent between compilation units, which is UB and can cause linking errors, and some parts of LLVM just crash on the empty name (see the linked issue).

As far as we know there is only one valid pattern that could use this, a `#[used]` static that is not referenced by the program at all. That is not UB, but the `export_name` is not required for that to work, just normal rust name mangling would do fine.

Technically this is a breaking change, but it seems unlikely that this actually breaks code in the wild that wasn't already broken. I'll leave it up to T-lang to determine what is required here (crater run, FCW, ...), but my gut feeling is that we could just merge this and nobody would notice.
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request May 9, 2026
…r=jdonszelmann

error on empty `export_name`

fixes rust-lang#155495

Using an empty string as the name makes LLVM make up a name. However this name can be inconsistent between compilation units, which is UB and can cause linking errors, and some parts of LLVM just crash on the empty name (see the linked issue).

As far as we know there is only one valid pattern that could use this, a `#[used]` static that is not referenced by the program at all. That is not UB, but the `export_name` is not required for that to work, just normal rust name mangling would do fine.

Technically this is a breaking change, but it seems unlikely that this actually breaks code in the wild that wasn't already broken. I'll leave it up to T-lang to determine what is required here (crater run, FCW, ...), but my gut feeling is that we could just merge this and nobody would notice.
rust-bors Bot pushed a commit that referenced this pull request May 9, 2026
…uwer

Rollup of 10 pull requests

Successful merges:

 - #148214 (Consider `Result<T, Uninhabited>` and `ControlFlow<Uninhabited, T>` to be equivalent to `T` for must use lint)
 - #149362 (Add Command::get_resolved_envs)
 - #155705 (Add `str::word_to_titlecase()` to `alloc`)
 - #155970 (Add mention of sendfile(2) and splice(2) to fs::copy() documentation.)
 - #156006 (Update a bunch of bootstrap dependencies to remove windows-target)
 - #155188 (Add regression test for issue 144329)
 - #155515 (error on empty `export_name`)
 - #155817 (validate `#[link_name = "..."]` & `#[link(name = "...")]` parameters)
 - #156107 (remove turbofish notation + use None / Some instead of Option:: (in match documentation))
 - #156133 (mark some panicking methods around Duration as track_caller)
rust-bors Bot pushed a commit that referenced this pull request May 10, 2026
Rollup of 11 pull requests

Successful merges:

 - #149362 (Add Command::get_resolved_envs)
 - #155705 (Add `str::word_to_titlecase()` to `alloc`)
 - #155970 (Add mention of sendfile(2) and splice(2) to fs::copy() documentation.)
 - #156006 (Update a bunch of bootstrap dependencies to remove windows-target)
 - #156169 (Change `SwitchInt` handling in dataflow analysis.)
 - #155188 (Add regression test for issue 144329)
 - #155515 (error on empty `export_name`)
 - #155817 (validate `#[link_name = "..."]` & `#[link(name = "...")]` parameters)
 - #156107 (remove turbofish notation + use None / Some instead of Option:: (in match documentation))
 - #156133 (mark some panicking methods around Duration as track_caller)
 - #156363 (`rustc_attr_parsing`: add `AcceptContext::expect_string_literal`)
rust-bors Bot pushed a commit that referenced this pull request May 10, 2026
Rollup of 11 pull requests

Successful merges:

 - #149362 (Add Command::get_resolved_envs)
 - #155705 (Add `str::word_to_titlecase()` to `alloc`)
 - #155970 (Add mention of sendfile(2) and splice(2) to fs::copy() documentation.)
 - #156006 (Update a bunch of bootstrap dependencies to remove windows-target)
 - #156169 (Change `SwitchInt` handling in dataflow analysis.)
 - #155188 (Add regression test for issue 144329)
 - #155515 (error on empty `export_name`)
 - #155817 (validate `#[link_name = "..."]` & `#[link(name = "...")]` parameters)
 - #156107 (remove turbofish notation + use None / Some instead of Option:: (in match documentation))
 - #156133 (mark some panicking methods around Duration as track_caller)
 - #156363 (`rustc_attr_parsing`: add `AcceptContext::expect_string_literal`)
rust-bors Bot pushed a commit that referenced this pull request May 10, 2026
Rollup of 11 pull requests

Successful merges:

 - #149362 (Add Command::get_resolved_envs)
 - #155705 (Add `str::word_to_titlecase()` to `alloc`)
 - #155970 (Add mention of sendfile(2) and splice(2) to fs::copy() documentation.)
 - #156006 (Update a bunch of bootstrap dependencies to remove windows-target)
 - #156169 (Change `SwitchInt` handling in dataflow analysis.)
 - #155188 (Add regression test for issue 144329)
 - #155515 (error on empty `export_name`)
 - #155817 (validate `#[link_name = "..."]` & `#[link(name = "...")]` parameters)
 - #156107 (remove turbofish notation + use None / Some instead of Option:: (in match documentation))
 - #156133 (mark some panicking methods around Duration as track_caller)
 - #156363 (`rustc_attr_parsing`: add `AcceptContext::expect_string_literal`)
@rust-bors
rust-bors Bot merged commit 6b93655 into rust-lang:main May 10, 2026
11 checks passed
@rustbot rustbot added this to the 1.97.0 milestone May 10, 2026
ehuss added a commit to ehuss/reference that referenced this pull request May 11, 2026
rust-lang/rust#155515 added a restriction
that the symbol name cannot be empty in the `export_name` attribute.

This now matches the behavior of link_name (see
rust-lang#2268).
@traviscross traviscross added the relnotes Marks issues that should be documented in the release notes of the next release. label May 19, 2026
ehuss added a commit to ehuss/reference that referenced this pull request May 26, 2026
rust-lang/rust#155515 added a restriction
that the symbol name cannot be empty in the `export_name` attribute.

This now matches the behavior of link_name (see
rust-lang#2268).
tmeijn pushed a commit to tmeijn/dotfiles that referenced this pull request Jul 10, 2026
This MR contains the following updates:

| Package | Update | Change |
|---|---|---|
| [rust](https://github.com/rust-lang/rust) | minor | `1.96.1` → `1.97.0` |

MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot).

**Proposed changes to behavior should be submitted there as MRs.**

---

### Release Notes

<details>
<summary>rust-lang/rust (rust)</summary>

### [`v1.97.0`](https://github.com/rust-lang/rust/blob/HEAD/RELEASES.md#Version-1970-2026-07-09)

[Compare Source](rust-lang/rust@1.96.1...1.97.0)

\==========================

<a id="1.97.0-Language"></a>

## Language

- [Consider `Result<T, Uninhabited>` and `ControlFlow<Uninhabited, T>` to be equivalent to `T` for must use lint](rust-lang/rust#148214)
- [Add allow-by-default `dead_code_pub_in_binary` lint for unused pub items in binary crates](rust-lang/rust#149509)
- [Stabilize the `div32`, `lam-bh`, `lamcas`, `ld-seq-sa` and `scq` target features](rust-lang/rust#154510)
- [Stabilize `cfg(target_has_atomic_primitive_alignment)`](rust-lang/rust#155006)
- [Allow trailing `self` in imports in more cases](rust-lang/rust#155137)

<a id="1.97.0-Platform-Support"></a>

## Platform Support

- [nvptx64-nvidia-cuda: drop support for old architectures and old ISAs](rust-lang/rust#152443)

Refer to Rust's [platform support page][platform-support-doc]
for more information on Rust's tiered platform support.

[platform-support-doc]: https://doc.rust-lang.org/rustc/platform-support.html

<a id="1.97.0-Stabilized-APIs"></a>

## Stabilized APIs

- [`Default for RepeatN`](https://doc.rust-lang.org/stable/std/iter/struct.RepeatN.html#impl-Default-for-RepeatN%3CA%3E)
- [`Copy for ffi::FromBytesUntilNulError`](https://doc.rust-lang.org/stable/std/ffi/struct.FromBytesUntilNulError.html#impl-Copy-for-FromBytesUntilNulError)
- [`Send for std::fs::File` on UEFI](rust-lang/rust#154003)
- [`<{integer}>::isolate_highest_one`](https://doc.rust-lang.org/stable/std/primitive.u32.html#method.isolate_highest_one)
- [`<{integer}>::isolate_lowest_one`](https://doc.rust-lang.org/stable/std/primitive.u32.html#method.isolate_lowest_one)
- [`<{integer}>::highest_one`](https://doc.rust-lang.org/stable/std/primitive.u32.html#method.highest_one)
- [`<{integer}>::lowest_one`](https://doc.rust-lang.org/stable/std/primitive.u32.html#method.lowest_one)
- [`<{integer}>::bit_width`](https://doc.rust-lang.org/stable/std/primitive.u32.html#method.bit_width)
- [`NonZero<{integer}>::isolate_highest_one`](https://doc.rust-lang.org/stable/std/num/struct.NonZero.html#method.isolate_highest_one)
- [`NonZero<{integer}>::isolate_lowest_one`](https://doc.rust-lang.org/stable/std/num/struct.NonZero.html#method.isolate_lowest_one)
- [`NonZero<{integer}>::highest_one`](https://doc.rust-lang.org/stable/std/num/struct.NonZero.html#method.highest_one)
- [`NonZero<{integer}>::lowest_one`](https://doc.rust-lang.org/stable/std/num/struct.NonZero.html#method.lowest_one)
- [`NonZero<{integer}>::bit_width`](https://doc.rust-lang.org/stable/std/num/struct.NonZero.html#method.bit_width)

These previously stable APIs are now stable in const contexts:

- [`char::is_control`](https://doc.rust-lang.org/stable/std/primitive.char.html#method.is_control)

<a id="1.97.0-Cargo"></a>

## Cargo

- [Stabilize `build.warnings` config.](rust-lang/cargo#16796) This controls how lint warnings from local packages are treated. Useful for enforcing a warning-free build in CI, replacing `-Dwarnings`. [docs](https://doc.rust-lang.org/nightly/cargo/reference/config.html#buildwarnings)
- [Stabilize `resolver.lockfile-path` config.](rust-lang/cargo#16694) This allows specifying the path to the lockfile to use when resolving dependencies. Useful when working with read-only source directories. [docs](https://doc.rust-lang.org/nightly/cargo/reference/config.html#resolverlockfile-path)
- [cargo-clean: Error when `--target-dir` doesn't look like a Cargo target directory.](rust-lang/cargo#16712) This prevents accidental deletion of non-target directories.
- [Add `-m` shorthand for `--manifest-path`](rust-lang/cargo#16858)
- [Remove `curl` dependency from `crates-io` crate](rust-lang/cargo#16936)

<a id="1.97.0-Rustdoc"></a>

## Rustdoc

- [Stabilize `--emit` flag](rust-lang/rust#146220)
- [Stabilize `--remap-path-prefix`](rust-lang/rust#155307)

<a id="1.97.0-Compatibility-Notes"></a>

## Compatibility Notes

- [Emit a future-compatibility warning when relying on `f32: From<{float}>` to constrain `{float}`](rust-lang/rust#139087)
- [Rust will use the v0 symbol mangling scheme by default.](rust-lang/rust#151994) This may cause some tools (such as debuggers or profilers, especially with old versions) to fail to demangle symbols emitted by Rust. It may also cause the formatting of text in backtraces to change.
- [Prevent deref coercions in `pin!`, in order to prevent unsoundness.](rust-lang/rust#153457) The most likely case where this might impact users is: writing `pin!(x)` where `x` has type `&mut T` will now always correctly produce a value of type `Pin<&mut &mut T>`, instead of sometimes allowing a coercion that produces a value of type `Pin<&mut T>`. This coercion was previously incorrectly allowed since Rust 1.88.0.
- [Deprecate `std::char` constants and functions](rust-lang/rust#153873)
- [Warn on linker output by default](rust-lang/rust#153968)
- [Remove hidden `f64` methods which have been deprecated since 1.0](rust-lang/rust#153975)
- [report the `varargs_without_pattern` lint in deps](rust-lang/rust#154599)
- [Forbid passing generic arguments to module path segments even if the module reexports a generic enum variant](rust-lang/rust#154971)
- [Error on invalid macho `link_section` specifier](rust-lang/rust#155065)
- The encoding of certain `enum`s [have changed](rust-lang/rust#155473).  This is not a breaking change, as it only applies to `enum`s without layout guarantees, but is noted here as we've seen people impacted from having made assumptions about the layout algorithm.
- [Error on `#[export_name = "..."]` where the name is empty](rust-lang/rust#155515)
- [Syntactically reject tuple index shorthands in struct patterns](rust-lang/rust#155698)
- [validate `#[link_name = "..."]` & `#[link(name = "...")]` parameters](rust-lang/rust#155817)
- On Windows, after calling `shutdown` on a socket to shut down the write side, attempting to write to the socket will now produce a `BrokenPipe` error rather than `Other`. [Map `WSAESHUTDOWN` to `io::ErrorKind::BrokenPipe`](rust-lang/rust#156063)

</details>

---

### Configuration

📅 **Schedule**: (UTC)

- Branch creation
  - At any time (no schedule defined)
- Automerge
  - At any time (no schedule defined)

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this MR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box

---

This MR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yNTYuMCIsInVwZGF0ZWRJblZlciI6IjQzLjI1Ni4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJSZW5vdmF0ZSBCb3QiLCJhdXRvbWF0aW9uOmJvdC1hdXRob3JlZCIsImRlcGVuZGVuY3ktdHlwZTo6bWlub3IiXX0=-->
eleboucher pushed a commit to eleboucher/towonel that referenced this pull request Jul 10, 2026
This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [rust](https://github.com/rust-lang/rust) |  | minor | `1.96.1` → `1.97.0` |
| rust | stage | minor | `1.96-bookworm` → `1.97-bookworm` |

---

### Release Notes

<details>
<summary>rust-lang/rust (rust)</summary>

### [`v1.97.0`](https://github.com/rust-lang/rust/blob/HEAD/RELEASES.md#Version-1970-2026-07-09)

[Compare Source](rust-lang/rust@1.96.1...1.97.0)

\==========================

<a id="1.97.0-Language"></a>

## Language

- [Consider `Result<T, Uninhabited>` and `ControlFlow<Uninhabited, T>` to be equivalent to `T` for must use lint](rust-lang/rust#148214)
- [Add allow-by-default `dead_code_pub_in_binary` lint for unused pub items in binary crates](rust-lang/rust#149509)
- [Stabilize the `div32`, `lam-bh`, `lamcas`, `ld-seq-sa` and `scq` target features](rust-lang/rust#154510)
- [Stabilize `cfg(target_has_atomic_primitive_alignment)`](rust-lang/rust#155006)
- [Allow trailing `self` in imports in more cases](rust-lang/rust#155137)

<a id="1.97.0-Platform-Support"></a>

## Platform Support

- [nvptx64-nvidia-cuda: drop support for old architectures and old ISAs](rust-lang/rust#152443)

Refer to Rust's [platform support page][platform-support-doc]
for more information on Rust's tiered platform support.

[platform-support-doc]: https://doc.rust-lang.org/rustc/platform-support.html

<a id="1.97.0-Stabilized-APIs"></a>

## Stabilized APIs

- [`Default for RepeatN`](https://doc.rust-lang.org/stable/std/iter/struct.RepeatN.html#impl-Default-for-RepeatN%3CA%3E)
- [`Copy for ffi::FromBytesUntilNulError`](https://doc.rust-lang.org/stable/std/ffi/struct.FromBytesUntilNulError.html#impl-Copy-for-FromBytesUntilNulError)
- [`Send for std::fs::File` on UEFI](rust-lang/rust#154003)
- [`<{integer}>::isolate_highest_one`](https://doc.rust-lang.org/stable/std/primitive.u32.html#method.isolate_highest_one)
- [`<{integer}>::isolate_lowest_one`](https://doc.rust-lang.org/stable/std/primitive.u32.html#method.isolate_lowest_one)
- [`<{integer}>::highest_one`](https://doc.rust-lang.org/stable/std/primitive.u32.html#method.highest_one)
- [`<{integer}>::lowest_one`](https://doc.rust-lang.org/stable/std/primitive.u32.html#method.lowest_one)
- [`<{integer}>::bit_width`](https://doc.rust-lang.org/stable/std/primitive.u32.html#method.bit_width)
- [`NonZero<{integer}>::isolate_highest_one`](https://doc.rust-lang.org/stable/std/num/struct.NonZero.html#method.isolate_highest_one)
- [`NonZero<{integer}>::isolate_lowest_one`](https://doc.rust-lang.org/stable/std/num/struct.NonZero.html#method.isolate_lowest_one)
- [`NonZero<{integer}>::highest_one`](https://doc.rust-lang.org/stable/std/num/struct.NonZero.html#method.highest_one)
- [`NonZero<{integer}>::lowest_one`](https://doc.rust-lang.org/stable/std/num/struct.NonZero.html#method.lowest_one)
- [`NonZero<{integer}>::bit_width`](https://doc.rust-lang.org/stable/std/num/struct.NonZero.html#method.bit_width)

These previously stable APIs are now stable in const contexts:

- [`char::is_control`](https://doc.rust-lang.org/stable/std/primitive.char.html#method.is_control)

<a id="1.97.0-Cargo"></a>

## Cargo

- [Stabilize `build.warnings` config.](rust-lang/cargo#16796) This controls how lint warnings from local packages are treated. Useful for enforcing a warning-free build in CI, replacing `-Dwarnings`. [docs](https://doc.rust-lang.org/nightly/cargo/reference/config.html#buildwarnings)
- [Stabilize `resolver.lockfile-path` config.](rust-lang/cargo#16694) This allows specifying the path to the lockfile to use when resolving dependencies. Useful when working with read-only source directories. [docs](https://doc.rust-lang.org/nightly/cargo/reference/config.html#resolverlockfile-path)
- [cargo-clean: Error when `--target-dir` doesn't look like a Cargo target directory.](rust-lang/cargo#16712) This prevents accidental deletion of non-target directories.
- [Add `-m` shorthand for `--manifest-path`](rust-lang/cargo#16858)
- [Remove `curl` dependency from `crates-io` crate](rust-lang/cargo#16936)

<a id="1.97.0-Rustdoc"></a>

## Rustdoc

- [Stabilize `--emit` flag](rust-lang/rust#146220)
- [Stabilize `--remap-path-prefix`](rust-lang/rust#155307)

<a id="1.97.0-Compatibility-Notes"></a>

## Compatibility Notes

- [Emit a future-compatibility warning when relying on `f32: From<{float}>` to constrain `{float}`](rust-lang/rust#139087)
- [Rust will use the v0 symbol mangling scheme by default.](rust-lang/rust#151994) This may cause some tools (such as debuggers or profilers, especially with old versions) to fail to demangle symbols emitted by Rust. It may also cause the formatting of text in backtraces to change.
- [Prevent deref coercions in `pin!`, in order to prevent unsoundness.](rust-lang/rust#153457) The most likely case where this might impact users is: writing `pin!(x)` where `x` has type `&mut T` will now always correctly produce a value of type `Pin<&mut &mut T>`, instead of sometimes allowing a coercion that produces a value of type `Pin<&mut T>`. This coercion was previously incorrectly allowed since Rust 1.88.0.
- [Deprecate `std::char` constants and functions](rust-lang/rust#153873)
- [Warn on linker output by default](rust-lang/rust#153968)
- [Remove hidden `f64` methods which have been deprecated since 1.0](rust-lang/rust#153975)
- [report the `varargs_without_pattern` lint in deps](rust-lang/rust#154599)
- [Forbid passing generic arguments to module path segments even if the module reexports a generic enum variant](rust-lang/rust#154971)
- [Error on invalid macho `link_section` specifier](rust-lang/rust#155065)
- The encoding of certain `enum`s [have changed](rust-lang/rust#155473).  This is not a breaking change, as it only applies to `enum`s without layout guarantees, but is noted here as we've seen people impacted from having made assumptions about the layout algorithm.
- [Error on `#[export_name = "..."]` where the name is empty](rust-lang/rust#155515)
- [Syntactically reject tuple index shorthands in struct patterns](rust-lang/rust#155698)
- [validate `#[link_name = "..."]` & `#[link(name = "...")]` parameters](rust-lang/rust#155817)
- On Windows, after calling `shutdown` on a socket to shut down the write side, attempting to write to the socket will now produce a `BrokenPipe` error rather than `Other`. [Map `WSAESHUTDOWN` to `io::ErrorKind::BrokenPipe`](rust-lang/rust#156063)

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xMDEuMSIsInVwZGF0ZWRJblZlciI6IjQzLjEwMS4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZS9jb250YWluZXIiLCJ0eXBlL21pbm9yIl19-->

Reviewed-on: https://codeberg.org/towonel/towonel/pulls/58
wip-sync pushed a commit to NetBSD/pkgsrc-wip that referenced this pull request Jul 11, 2026
Package updates relative to rust196:
 * Version & checksum changes
 * Applied patches to updated vendored crates

Upstream changes:

Version 1.97.0 (2026-07-09)
==========================

Language
--------
- [Consider `Result<T, Uninhabited>` and `ControlFlow<Uninhabited,
  T>` to be equivalent to `T` for must use lint]
  (rust-lang/rust#148214)
- [Add allow-by-default `dead_code_pub_in_binary` lint for unused
  pub items in binary crates] (rust-lang/rust#149509)
- [Stabilize the `div32`, `lam-bh`, `lamcas`, `ld-seq-sa` and `scq`
  target features] (rust-lang/rust#154510)
- [Stabilize `cfg(target_has_atomic_primitive_alignment)`]
  (rust-lang/rust#155006)
- [Allow trailing `self` in imports in more cases]
  (rust-lang/rust#155137)

Platform Support
----------------
- [nvptx64-nvidia-cuda: drop support for old architectures and old ISAs]
  (rust-lang/rust#152443)

Refer to Rust's [platform support page][platform-support-doc]
for more information on Rust's tiered platform support.

[platform-support-doc]: https://doc.rust-lang.org/rustc/platform-support.html

Stabilized APIs
---------------

- [`Default for RepeatN`]
  (https://doc.rust-lang.org/stable/std/iter/struct.RepeatN.html#impl-Default-for-RepeatN%3CA%3E)
- [`Copy for ffi::FromBytesUntilNulError`]
  (https://doc.rust-lang.org/stable/std/ffi/struct.FromBytesUntilNulError.html#impl-Copy-for-FromBytesUntilNulError)
- [`Send for std::fs::File` on UEFI]
  (rust-lang/rust#154003)
- [`<{integer}>::isolate_highest_one`]
  (https://doc.rust-lang.org/stable/std/primitive.u32.html#method.isolate_highest_one)
- [`<{integer}>::isolate_lowest_one`]
  (https://doc.rust-lang.org/stable/std/primitive.u32.html#method.isolate_lowest_one)
- [`NonZero<{integer}>::isolate_highest_one`]
  (https://doc.rust-lang.org/stable/std/num/struct.NonZero.html#method.isolate_highest_one)
- [`NonZero<{integer}>::isolate_lowest_one`]
  (https://doc.rust-lang.org/stable/std/num/struct.NonZero.html#method.isolate_lowest_one)
- [`<{integer}>::bit_width`]
  (https://doc.rust-lang.org/stable/std/primitive.u32.html#method.bit_width)
- [`<{integer}>::lowest_one`]
  (https://doc.rust-lang.org/stable/std/primitive.u32.html#method.lowest_one)
- [`<{integer}>::highest_one`]
  (https://doc.rust-lang.org/stable/std/primitive.u32.html#method.highest_one)
- [`NonZero<{integer}>::bit_width`]
  (https://doc.rust-lang.org/stable/std/num/struct.NonZero.html#method.bit_width)
- [`NonZero<{integer}>::highest_one`]
  (https://doc.rust-lang.org/stable/std/num/struct.NonZero.html#method.highest_one)
- [`NonZero<{integer}>::lowest_one`]
  (https://doc.rust-lang.org/stable/std/num/struct.NonZero.html#method.lowest_one)

These previously stable APIs are now stable in const contexts:

- [`char::is_control`]
  (https://doc.rust-lang.org/stable/std/primitive.char.html#method.is_control)

Cargo
-----
- [Stabilize `build.warnings` config.]
  (rust-lang/cargo#16796) This controls
  how lint warnings from local packages are treated. Useful for
  enforcing a warning-free build in CI, replacing `-Dwarnings`.
  [docs]
  (https://doc.rust-lang.org/nightly/cargo/reference/config.html#buildwarnings)
- [Stabilize `resolver.lockfile-path` config.]
  (rust-lang/cargo#16694) This allows
  specifying the path to the lockfile to use when resolving
  dependencies. Useful when working with read-only source directories.  [docs]
  (https://doc.rust-lang.org/nightly/cargo/reference/config.html#resolverlockfile-path)
- [cargo-clean: Error when `--target-dir` doesn't look like a Cargo
  target directory.] (rust-lang/cargo#16712)
  This prevents accidental deletion of non-target directories.
- [Add `-m` shorthand for `--manifest-path`]
  (rust-lang/cargo#16858)
- [Remove `curl` dependency from `crates-io` crate]
  (rust-lang/cargo#16936)

Rustdoc
-----
- [Stabilize `--emit` flag]
  (rust-lang/rust#146220)
- [Stabilize `--remap-path-prefix`]
  (rust-lang/rust#155307)

Compatibility Notes
-------------------
- [Emit a future-compatibility warning when relying on `f32:
  From<{float}>` to constrain `{float}`]
  (rust-lang/rust#139087)
- [Rust will use the v0 symbol mangling scheme by default.]
  (rust-lang/rust#151994) This may cause
  some tools (such as debuggers or profilers, especially with old
  versions) to fail to demangle symbols emitted by Rust. It may
  also cause the formatting of text in backtraces to change.
- [Prevent deref coercions in `pin!`, in order to prevent unsoundness.]
  (rust-lang/rust#153457) The most likely
  case where this might impact users is: writing `pin!(x)` where
  `x` has type `&mut T` will now always correctly produce a value
  of type `Pin<&mut &mut T>`, instead of sometimes allowing a
  coercion that produces a value of type `Pin<&mut T>`. This coercion
  was previously incorrectly allowed since Rust 1.88.0.
- [Deprecate `std::char` constants and functions]
  (rust-lang/rust#153873)
- [Warn on linker output by default]
  (rust-lang/rust#153968)
- [Remove hidden `f64` methods which have been deprecated since 1.0]
  (rust-lang/rust#153975)
- [report the `varargs_without_pattern` lint in deps]
  (rust-lang/rust#154599)
- [Forbid passing generic arguments to module path segments even
  if the module reexports a generic enum variant]
  (rust-lang/rust#154971)
- [Error on invalid macho `link_section` specifier]
  (rust-lang/rust#155065)
- The encoding of certain `enum`s [have changed]
  (rust-lang/rust#155473).  This is not a
  breaking change, as it only applies to `enum`s without layout
  guarantees, but is noted here as we've seen people impacted from
  having made assumptions about the layout algorithm.
- [Error on `#[export_name = "..."]` where the name is empty]
  (rust-lang/rust#155515)
- [Syntactically reject tuple index shorthands in struct patterns]
  (rust-lang/rust#155698)
- [validate `#[link_name = "..."]` & `#[link(name = "...")]` parameters]
  (rust-lang/rust#155817)
- On Windows, after calling `shutdown` on a socket to shut down
  the write side, attempting to write to the socket will now produce
  a `BrokenPipe` error rather than `Other`. [Map `WSAESHUTDOWN` to
  `io::ErrorKind::BrokenPipe`]
  (rust-lang/rust#156063)
jimsynz added a commit to jimsynz/neonfs that referenced this pull request Jul 19, 2026
This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [actions/cache](https://github.com/actions/cache) | action | major | `v5` → `v6` |
| [actions/checkout](https://github.com/actions/checkout) | action | major | `v6` → `v7` |
| [aes-gcm](https://github.com/RustCrypto/AEADs) | dependencies | minor | `0.10` → `0.11` |
| debian | stage | patch | `trixie-20260610` → `13` |
| debian | final | patch | `trixie-20260610` → `13` |
| [elixir](https://elixir-lang.org/) ([source](https://github.com/elixir-lang/elixir)) |  | patch | `1.20.1` → `1.20.2` |
| [erlang](https://github.com/erlang/otp) |  | patch | `29.0.2` → `29.0.3` |
| [goreleaser/nfpm](https://github.com/goreleaser/nfpm) |  | minor | `v2.46.3` → `v2.47.0` |
| [ra](https://hex.pm/packages/ra) ([source](https://github.com/rabbitmq/ra)) | prod | patch | `3.1.8` → `3.1.9` |
| registry.k8s.io/sig-storage/csi-resizer |  | patch | `v2.2.0` → `v2.2.1` |
| [req](https://hex.pm/packages/req) ([source](https://github.com/wojtekmach/req)) | dev | patch | `0.6.2` → `0.6.3` |
| [req](https://hex.pm/packages/req) ([source](https://github.com/wojtekmach/req)) | dev | patch | `~> 0.5` → `~> 0.6` |
| [rust](https://github.com/rust-lang/rust) |  | minor | `1.96.0` → `1.97.1` |
| [serde](https://serde.rs) ([source](https://github.com/serde-rs/serde)) | dependencies | patch | `1.0.228` → `1.0.229` |
| [stream_data](https://hex.pm/packages/stream_data) ([source](https://github.com/whatyouhide/stream_data)) | dev | minor | `1.3.0` → `1.4.0` |
| [stream_data](https://hex.pm/packages/stream_data) ([source](https://github.com/whatyouhide/stream_data)) | prod | minor | `1.3.0` → `1.4.0` |
| [thiserror](https://github.com/dtolnay/thiserror) | dependencies | patch | `2.0.18` → `2.0.19` |

---

### Release Notes

<details>
<summary>actions/cache (actions/cache)</summary>

### [`v6.1.0`](https://github.com/actions/cache/releases/tag/v6.1.0)

[Compare Source](actions/cache@v6.0.0...v6.1.0)

##### What's Changed

- Bump [@&#8203;actions/cache](https://github.com/actions/cache) to v6.1.0 - handle read-only cache access by [@&#8203;jasongin](https://github.com/jasongin) in [#&#8203;1768](actions/cache#1768)

**Full Changelog**: <actions/cache@v6...v6.1.0>

### [`v6.0.0`](https://github.com/actions/cache/releases/tag/v6.0.0)

[Compare Source](actions/cache@v6.0.0...v6.0.0)

##### What's Changed

- Update packages, migrate to ESM by [@&#8203;Samirat](https://github.com/Samirat) in [#&#8203;1760](actions/cache#1760)

**Full Changelog**: <actions/cache@v5...v6.0.0>

### [`v6`](actions/cache@v5.1.0...v6.0.0)

[Compare Source](actions/cache@v5.1.0...v6.0.0)

</details>

<details>
<summary>actions/checkout (actions/checkout)</summary>

### [`v7.0.0`](https://github.com/actions/checkout/blob/HEAD/CHANGELOG.md#v700)

[Compare Source](actions/checkout@v7.0.0...v7.0.0)

- Block checking out fork PR for pull\_request\_target and workflow\_run by [@&#8203;aiqiaoy](https://github.com/aiqiaoy) in [#&#8203;2454](actions/checkout#2454)
- Bump actions/publish-immutable-action from 0.0.3 to 0.0.4 in the minor-actions-dependencies group across 1 directory by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;2458](actions/checkout#2458)
- Bump flatted from 3.3.1 to 3.4.2 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;2460](actions/checkout#2460)
- Bump js-yaml from 4.1.0 to 4.2.0 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;2461](actions/checkout#2461)
- Bump [@&#8203;actions/core](https://github.com/actions/core) and [@&#8203;actions/tool-cache](https://github.com/actions/tool-cache) and Remove uuid by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;2459](actions/checkout#2459)
- upgrade module to esm and update dependencies by [@&#8203;aiqiaoy](https://github.com/aiqiaoy) in [#&#8203;2463](actions/checkout#2463)
- Bump the minor-npm-dependencies group across 1 directory with 3 updates by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;2462](actions/checkout#2462)

### [`v7`](https://github.com/actions/checkout/blob/HEAD/CHANGELOG.md#v701)

[Compare Source](actions/checkout@v6.0.3...v7.0.0)

- Bump github/codeql-action from 3 to 4 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;2475](actions/checkout#2475)
- Bump actions/setup-node from 4 to 6 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;2477](actions/checkout#2477)
- Bump docker/build-push-action from 6.5.0 to 7.2.0 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;2478](actions/checkout#2478)
- Bump docker/login-action from 3.3.0 to 4.2.0 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;2479](actions/checkout#2479)
- Bump actions/checkout from 6 to 7 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;2488](actions/checkout#2488)
- Bump actions/upload-artifact from 4 to 7 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;2476](actions/checkout#2476)
- eslint 9 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;2474](actions/checkout#2474)
- Bump the minor-actions-dependencies group with 2 updates by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;2499](actions/checkout#2499)
- skip running unsafe pr check if input is default by [@&#8203;aiqiaoy](https://github.com/aiqiaoy) in [#&#8203;2518](actions/checkout#2518)
- trim only ascii whitespace for branch by [@&#8203;aiqiaoy](https://github.com/aiqiaoy) in [#&#8203;2521](actions/checkout#2521)
- escape values passed to --unset by [@&#8203;aiqiaoy](https://github.com/aiqiaoy) in [#&#8203;2530](actions/checkout#2530)

</details>

<details>
<summary>RustCrypto/AEADs (aes-gcm)</summary>

### [`v0.11.0`](RustCrypto/AEADs@aes-gcm-v0.10.3...aes-gcm-v0.11.0)

[Compare Source](RustCrypto/AEADs@aes-gcm-v0.10.3...aes-gcm-v0.11.0)

</details>

<details>
<summary>elixir-lang/elixir (elixir)</summary>

### [`v1.20.2`](https://github.com/elixir-lang/elixir/releases/tag/v1.20.2)

[Compare Source](elixir-lang/elixir@v1.20.1...v1.20.2)

##### 1. Enhancements

##### Elixir

- \[Kernel.ParallelCompiler] Include per-module type checking times when compiler profiling is enabled with `profile: :time`

##### 2. Bug fixes

##### Elixir

- \[Kernel] Fix binary comprehensions with sizes when options such as `:uniq` or `:into` are used
- \[Kernel] Improve compiler error messages when `quote` with `unquote` is used inside a pattern or guard
- \[Kernel] Restore the compiler optimization of `Kernel.put_elem/3` to emit `:erlang.setelement/3`
- \[Module] Fix type checking when applying an empty function type
- \[Module] Fix type checking of bitstring patterns that reuse variables
- \[Module] Fix type information for `__info__(:struct)` to include the `:required` key
- \[Module] Fix type operations on map and optional keys during difference/intersection, including open keys and empty intersections
- \[Module] Fix typing of list types involving dynamic or empty lists
- \[Module] Include bitstrings as a possible domain key in the type system
- \[Module] Preserve file metadata from each clause in type system warnings
- \[Module] Fix type warnings for protocol implementations whose protocol module defines additional callbacks
- \[Module] Raise clearer type checking errors when an expected struct is removed or redefined during compilation

##### Mix

- \[mix compile] Avoid unnecessary umbrella recompilation when a path dependency's manifest is newer but unchanged
- \[mix deps.compile] Recompile fetched dependencies when their compile-time environment changes

</details>

<details>
<summary>erlang/otp (erlang)</summary>

### [`v29.0.3`](https://github.com/erlang/otp/releases/tag/OTP-29.0.3): OTP 29.0.3

[Compare Source](erlang/otp@OTP-29.0.2...OTP-29.0.3)

```
Patch Package:           OTP 29.0.3
Git Tag:                 OTP-29.0.3
Date:                    2026-07-02
Trouble Report Id:       OTP-20173, OTP-20183, OTP-20185, OTP-20186,
                         OTP-20190, OTP-20191, OTP-20194, OTP-20196,
                         OTP-20197, OTP-20198, OTP-20199, OTP-20200,
                         OTP-20201, OTP-20206, OTP-20207, OTP-20208,
                         OTP-20215, OTP-20216, OTP-20217, OTP-20220,
                         OTP-20222, OTP-20226, OTP-20227, OTP-20230,
                         OTP-20231, OTP-20232, OTP-20233
Seq num:                 CVE-2026-53422, CVE-2026-54886,
                         CVE-2026-54887, CVE-2026-54891,
                         CVE-2026-55950, CVE-2026-55952, ERIERL-1333,
                         GH-SA-7wp4-pc27-2vj9, GH-SA-h9pw-h5w4-h976,
                         PR-11209, PR-11215, PR-11219, PR-11230,
                         PR-11239, PR-11244, PR-11247, PR-11250,
                         PR-11259, PR-11268, PR-11269, PR-11270,
                         PR-11271, PR-11281, PR-11282, PR-11283,
                         PR-11289, PR-11294, PR-11295, PR-11299,
                         PR-11302, PR-11306, PR-11307, PR-11309,
                         PR-11311
System:                  OTP
Release:                 29
Application:             common_test-1.31.1, compiler-10.0.2,
                         crypto-5.9.1, dialyzer-6.0.2, erts-17.0.3,
                         kernel-11.0.3, public_key-1.21.3, ssh-6.0.2,
                         ssl-11.7.3, stdlib-8.0.2
Predecessor:             OTP 29.0.2
```

Check out the git tag OTP-29.0.3, and build a full OTP system including documentation. Apply one or more applications from this build as patches to your installation using the 'otp\_patch\_apply' tool. For information on install requirements, see descriptions for each application version below.

### common\_test-1.31.1

The common\_test-1.31.1 application can be applied independently of other applications on a full OTP 29 installation.

#### Fixed Bugs and Malfunctions

- Fixed a crash in ct\_netconfc that occurred when the remote server closed the SSH connection during NETCONF subsystem negotiation.

  Own Id: OTP-20191\
  Related Id(s): ERIERL-1333, [PR-11230]

> #### Full runtime dependencies of common\_test-1.31.1
>
> compiler-10.0, crypto-4.5, debugger-4.1, erts-7.0, ftp-1.0, inets-6.0, kernel-11.0, observer-2.1, runtime\_tools-1.8.16, sasl-2.5, snmp-5.1.2, ssh-4.0, stdlib-8.0, syntax\_tools-1.7, tools-3.2, xmerl-1.3.8

### compiler-10.0.2

The compiler-10.0.2 application can be applied independently of other applications on a full OTP 29 installation.

#### Fixed Bugs and Malfunctions

- Several compiler bugs that could crash the compiler or generate incorrect code in rare circumstances have been fixed.

  Own Id: OTP-20222\
  Related Id(s): [PR-11219]

> #### Full runtime dependencies of compiler-10.0.2
>
> crypto-5.1, erts-13.0, kernel-8.4, stdlib-8.0

### crypto-5.9.1

The crypto-5.9.1 application can be applied independently of other applications on a full OTP 29 installation.

#### Fixed Bugs and Malfunctions

- `crypto:compute_key/4` for `eddh` and `crypto:generate_key/2,3` for `eddh`/`eddsa` now raise an `error:{notsup, Info, Description}` exception instead of returning the atom `notsup` when the underlying cryptolib lacks support.

  Own Id: OTP-20215\
  Related Id(s): [PR-11302]

> #### Full runtime dependencies of crypto-5.9.1
>
> erts-9.0, kernel-6.0, stdlib-3.9

### dialyzer-6.0.2

The dialyzer-6.0.2 application can be applied independently of other applications on a full OTP 29 installation.

#### Fixed Bugs and Malfunctions

- Fix a bug with native record sets in `erl_types.erl`

  Own Id: OTP-20201

> #### Full runtime dependencies of dialyzer-6.0.2
>
> compiler-10.0, erts-12.0, kernel-8.0, stdlib-5.0, syntax\_tools-2.0

### erts-17.0.3

The erts-17.0.3 application can be applied independently of other applications on a full OTP 29 installation.

#### Fixed Bugs and Malfunctions

- Fixed an undefined behavior in the internal `erts_qsort()` function, which could have been the cause of a beam crash seen when updating large maps.

  Own Id: OTP-20185\
  Related Id(s): [PR-11215]

- Calculating `bxor` of the largest supported positive integer (`erlang:system_info(max_integer)`) and `-1` would return `[]` instead of a raising a `system_limit` exception.

  Own Id: OTP-20208\
  Related Id(s): [PR-11269]

- Fix possible race between `ets:delete/1` and terminating process with a fixation on the same table.

  Own Id: OTP-20217\
  Related Id(s): [PR-11283]

- A few code generation issues for the JIT on AArch64 (ARM64) have been fixed.

  For all platforms, the loader will reject some invalid BEAM files earlier.

  Own Id: OTP-20226\
  Related Id(s): [PR-11299]

- On 32-bit computers, the `md5` BIFs would return an incorrect MD5 checksum for data of size 4GiB or more.

  Own Id: OTP-20227\
  Related Id(s): [PR-11289]

> #### Full runtime dependencies of erts-17.0.3
>
> kernel-9.0, sasl-3.3, stdlib-4.1

### kernel-11.0.3

The kernel-11.0.3 application can be applied independently of other applications on a full OTP 29 installation.

#### Fixed Bugs and Malfunctions

- inet:info/1 could crash when calling for a closing (port) socket.

  Own Id: OTP-20173

- Handling of the truncation bit in `inet_res` has been fixed so it properly falls back to querying over TCP after a truncated UDP reply.

  This fixes a bug introduced in OTP-28.4.2 - kernel-10.6.2 making a truncated UDP answer fail to parse and never execute the fallback, instead the name resolve operation fails.

  Own Id: OTP-20199\
  Related Id(s): [PR-11247]

> #### Full runtime dependencies of kernel-11.0.3
>
> crypto-5.8, erts-17.0, sasl-3.0, stdlib-8.0

### public\_key-1.21.3

The public\_key-1.21.3 application can be applied independently of other applications on a full OTP 29 installation.

#### Fixed Bugs and Malfunctions

- Hardened OCSP response verification by using constant-time hash comparisons and rejecting responses exceeding 100 KB before ASN.1 decoding.

  Own Id: OTP-20197\
  Related Id(s): [PR-11239]

> #### Full runtime dependencies of public\_key-1.21.3
>
> asn1-5.0, crypto-5.8, erts-13.0, kernel-8.0, stdlib-4.0

### ssh-6.0.2

The ssh-6.0.2 application can be applied independently of other applications on a full OTP 29 installation.

#### Fixed Bugs and Malfunctions

- Fixed a path-existence oracle in the SFTP server where `SSH_FXP_REALPATH` requests with `..` components could bypass the configured root directory isolation, allowing an authenticated client to determine whether arbitrary paths exist on the host filesystem.

  Own Id: OTP-20183\
  Related Id(s): [GH-SA-h9pw-h5w4-h976], [PR-11294], [CVE-2026-53422]

- Fixed an infinite loop in the SFTP server triggered when receiving `SSH_MSG_CHANNEL_EXTENDED_DATA` on an SFTP channel, which caused the channel process to spin indefinitely on CPU without consuming its message queue.

  Own Id: OTP-20186\
  Related Id(s): [GH-SA-7wp4-pc27-2vj9], [PR-11295], [CVE-2026-54886]

- Fixed mlkem768x25519 hybrid key exchange failing intermittently with "incorrect signature" when the X25519 shared secret had a leading zero byte. The shared secret is now encoded as a fixed-width 32-byte string per the specification.

  Own Id: OTP-20196\
  Related Id(s): [PR-11209]

- Fixed a race condition where SSH keepalive responses could be matched to unrelated pending requests due to incorrect request queue ordering. Requests are now matched in the order they were sent.

  Own Id: OTP-20198\
  Related Id(s): [PR-11244]

- The SFTP server now caps the read length in `SSH_FXP_READ` requests to 255 KiB (matching OpenSSH's `SFTP_MAX_READ_LENGTH`), preventing excessive memory allocation when clients request large reads.

  Own Id: OTP-20200\
  Related Id(s): [PR-11259]

- Removed a server-side workaround (OTP-14827, introduced in OTP 20) that accepted SHA-1 user-auth signatures from clients identifying as OpenSSH 7.x when rsa-sha2-\* was negotiated. The workaround addressed a distro-specific build issue in 2017 that no longer exists. Clients affected by this removal (extremely unlikely — requires a 10-year-old unpatched OpenSSH build) will see authentication failures and must upgrade.

  Own Id: OTP-20206\
  Related Id(s): [PR-11268]

> #### Full runtime dependencies of ssh-6.0.2
>
> crypto-5.7, erts-14.0, kernel-10.3, public\_key-1.6.1, runtime\_tools-1.15.1, stdlib-8.0

### ssl-11.7.3

Note! The ssl-11.7.3 application *cannot* be applied independently of other applications on an arbitrary OTP 29 installation.

```
   On a full OTP 29 installation, also the following runtime
   dependency has to be satisfied:
   -- public_key-1.21.1 (first satisfied in OTP 29.0.1)
```

#### Fixed Bugs and Malfunctions

- Correct small behavior bugs that occasionally could cause DTLS connection errors, unwanted behavior for legacy DHE\_DSS, hiding of a distribution config error, and possible unorderly process tree shutdown.

  Own Id: OTP-20190\
  Related Id(s): [PR-11250]

- Initialize DTLS cookie to random value to avoid DoS attack with forged cookie during startup window.

  Own Id: OTP-20194\
  Related Id(s): [PR-11271], [CVE-2026-54887]

- Guard TLS client for MITM injection of application data during "plain-text-window" during handshake.

  Own Id: OTP-20207\
  Related Id(s): [PR-11270], [CVE-2026-54891]

- Improve error handling of TLS PSK sending ILLIGAL\_PARMETER alert if binders and PSK-identities are not matched. Also mend recovery mechanism of ticket and session stores to be as resilient as possible to intermediate bugs.

  Own Id: OTP-20216\
  Related Id(s): [PR-11282], [CVE-2026-55952]

- Fix race condition that could be used to DoS attack DTLS servers.

  Own Id: OTP-20220\
  Related Id(s): [PR-11306], [CVE-2026-55950]

- A TLS-1.3 stateless session ticket with obfuscated\_ticket\_age set to zero was incorrectly accepted without checking the server-side ticket lifetime or the RFC 8446 Section 8.3 freshness window. The server now always validates ticket age using its own timestamp regardless of the client-reported age value.

  Own Id: OTP-20230\
  Related Id(s): [PR-11307]

- TLS-1.3 client rejects a second HelloRetryRequest as requiered in RFC 8446 Section 4.1.4

  Own Id: OTP-20231\
  Related Id(s): [PR-11309]

- A busy client node could self-trigger a ticket store crash if unlucky with scheduling if auto mode is used.

  Own Id: OTP-20232\
  Related Id(s): [PR-11311]

- Correct spec for CRL API

  Own Id: OTP-20233\
  Related Id(s): [PR-11281]

> #### Full runtime dependencies of ssl-11.7.3
>
> crypto-5.8, erts-16.0, inets-5.10.7, kernel-10.3, public\_key-1.21.1, runtime\_tools-1.15.1, stdlib-7.0

### stdlib-8.0.2

The stdlib-8.0.2 application can be applied independently of other applications on a full OTP 29 installation.

#### Fixed Bugs and Malfunctions

- Several compiler bugs that could crash the compiler or generate incorrect code in rare circumstances have been fixed.

  Own Id: OTP-20222\
  Related Id(s): [PR-11219]

> #### Full runtime dependencies of stdlib-8.0.2
>
> compiler-5.0, crypto-4.5, erts-16.0.3, kernel-11.0, sasl-3.0, syntax\_tools-3.2.1

### Thanks to

Cole Christensen, Nick Krichevsky, Stefan Grundmann

[cve-2026-53422]: https://nvd.nist.gov/vuln/detail/CVE-2026-53422

[cve-2026-54886]: https://nvd.nist.gov/vuln/detail/CVE-2026-54886

[cve-2026-54887]: https://nvd.nist.gov/vuln/detail/CVE-2026-54887

[cve-2026-54891]: https://nvd.nist.gov/vuln/detail/CVE-2026-54891

[cve-2026-55950]: https://nvd.nist.gov/vuln/detail/CVE-2026-55950

[cve-2026-55952]: https://nvd.nist.gov/vuln/detail/CVE-2026-55952

[gh-sa-7wp4-pc27-2vj9]: https://github.com/erlang/otp/issues/SA-7wp4-pc27-2vj9

[gh-sa-h9pw-h5w4-h976]: https://github.com/erlang/otp/issues/SA-h9pw-h5w4-h976

[pr-11209]: erlang/otp#11209

[pr-11215]: erlang/otp#11215

[pr-11219]: erlang/otp#11219

[pr-11230]: erlang/otp#11230

[pr-11239]: erlang/otp#11239

[pr-11244]: erlang/otp#11244

[pr-11247]: erlang/otp#11247

[pr-11250]: erlang/otp#11250

[pr-11259]: erlang/otp#11259

[pr-11268]: erlang/otp#11268

[pr-11269]: erlang/otp#11269

[pr-11270]: erlang/otp#11270

[pr-11271]: erlang/otp#11271

[pr-11281]: erlang/otp#11281

[pr-11282]: erlang/otp#11282

[pr-11283]: erlang/otp#11283

[pr-11289]: erlang/otp#11289

[pr-11294]: erlang/otp#11294

[pr-11295]: erlang/otp#11295

[pr-11299]: erlang/otp#11299

[pr-11302]: erlang/otp#11302

[pr-11306]: erlang/otp#11306

[pr-11307]: erlang/otp#11307

[pr-11309]: erlang/otp#11309

[pr-11311]: erlang/otp#11311

</details>

<details>
<summary>goreleaser/nfpm (goreleaser/nfpm)</summary>

### [`v2.47.0`](https://github.com/goreleaser/nfpm/releases/tag/v2.47.0)

[Compare Source](goreleaser/nfpm@v2.46.3...v2.47.0)

##### Changelog

##### New Features

- [`5c2f7ca`](goreleaser/nfpm@5c2f7ca): feat: RiscV64 support ([#&#8203;1091](goreleaser/nfpm#1091)) ([@&#8203;ahqsoftwares](https://github.com/ahqsoftwares))
- [`64b788a`](goreleaser/nfpm@64b788a): feat: add Requires(Post) for RPMS ([#&#8203;1085](goreleaser/nfpm#1085)) ([@&#8203;teddelin](https://github.com/teddelin))
- [`dc96073`](goreleaser/nfpm@dc96073): feat: add fang support for styled CLI output ([#&#8203;1068](goreleaser/nfpm#1068)) ([@&#8203;caarlos0](https://github.com/caarlos0))

##### Security updates

- [`060af04`](goreleaser/nfpm@060af04): sec(deps): update golang.org/x/crypto ([@&#8203;caarlos0](https://github.com/caarlos0))
- [`f769631`](goreleaser/nfpm@f769631): sec(deps): update golang.org/x/net ([@&#8203;caarlos0](https://github.com/caarlos0))

##### Bug fixes

- [`3118ec1`](goreleaser/nfpm@3118ec1): fix: tolerate empty overrides packager clause ([#&#8203;1080](goreleaser/nfpm#1080)) ([@&#8203;dleske](https://github.com/dleske))

##### Dependency updates

- [`a2d9ce5`](goreleaser/nfpm@a2d9ce5): feat(deps): go1.26.4 ([@&#8203;caarlos0](https://github.com/caarlos0))
- [`9b16218`](goreleaser/nfpm@9b16218): fix(deps): bump alpine from 3.23.3 to 3.23.4 ([#&#8203;1075](goreleaser/nfpm#1075)) ([@&#8203;dependabot](https://github.com/dependabot)\[bot])
- [`e3102b3`](goreleaser/nfpm@e3102b3): fix(deps): bump alpine from 3.23.3 to 3.23.4 in /testdata/acceptance ([#&#8203;1076](goreleaser/nfpm#1076)) ([@&#8203;dependabot](https://github.com/dependabot)\[bot])
- [`62c555e`](goreleaser/nfpm@62c555e): fix(deps): bump alpine from 3.23.4 to 3.24.0 ([#&#8203;1098](goreleaser/nfpm#1098)) ([@&#8203;dependabot](https://github.com/dependabot)\[bot])
- [`071ae18`](goreleaser/nfpm@071ae18): fix(deps): bump alpine from 3.23.4 to 3.24.0 in /testdata/acceptance ([#&#8203;1099](goreleaser/nfpm#1099)) ([@&#8203;dependabot](https://github.com/dependabot)\[bot])

##### Build process updates

- [`4c62d34`](goreleaser/nfpm@4c62d34): ci(deps): bump github/codeql-action in the actions group ([#&#8203;1083](goreleaser/nfpm#1083)) ([@&#8203;dependabot](https://github.com/dependabot)\[bot])
- [`38a05de`](goreleaser/nfpm@38a05de): ci(deps): bump the actions group across 1 directory with 3 updates ([#&#8203;1096](goreleaser/nfpm#1096)) ([@&#8203;dependabot](https://github.com/dependabot)\[bot])
- [`6fe4da4`](goreleaser/nfpm@6fe4da4): ci(deps): bump the actions group across 1 directory with 7 updates ([#&#8203;1095](goreleaser/nfpm#1095)) ([@&#8203;dependabot](https://github.com/dependabot)\[bot])
- [`cd95f9f`](goreleaser/nfpm@cd95f9f): ci(deps): bump the actions group with 2 updates ([#&#8203;1078](goreleaser/nfpm#1078)) ([@&#8203;dependabot](https://github.com/dependabot)\[bot])
- [`8f9cbef`](goreleaser/nfpm@8f9cbef): ci(deps): bump the actions group with 3 updates ([#&#8203;1090](goreleaser/nfpm#1090)) ([@&#8203;dependabot](https://github.com/dependabot)\[bot])
- [`9ff0e2f`](goreleaser/nfpm@9ff0e2f): ci(deps): bump the actions group with 4 updates ([#&#8203;1086](goreleaser/nfpm#1086)) ([@&#8203;dependabot](https://github.com/dependabot)\[bot])
- [`2ce1832`](goreleaser/nfpm@2ce1832): ci(deps): bump the actions group with 5 updates ([#&#8203;1074](goreleaser/nfpm#1074)) ([@&#8203;dependabot](https://github.com/dependabot)\[bot])
- [`1bd2fed`](goreleaser/nfpm@1bd2fed): ci: fix docs build test ([@&#8203;caarlos0](https://github.com/caarlos0))
- [`4695cdc`](goreleaser/nfpm@4695cdc): ci: fix license check ([@&#8203;caarlos0](https://github.com/caarlos0))
- [`a40b461`](goreleaser/nfpm@a40b461): ci: update build ([@&#8203;caarlos0](https://github.com/caarlos0))

##### Other work

- [`d16d75f`](goreleaser/nfpm@d16d75f): docs(deps): update hextra ([@&#8203;caarlos0](https://github.com/caarlos0))
- [`c6a6a27`](goreleaser/nfpm@c6a6a27): docs: update cmd docs ([@&#8203;caarlos0](https://github.com/caarlos0))

**Full Changelog**: <goreleaser/nfpm@v2.46.3...v2.47.0>

##### Helping out

This release is only possible thanks to **all** the support of **awesome people**!

Want to be one of them?
You can [sponsor](https://goreleaser.com/sponsors/) or [contribute with code](https://goreleaser.com/contributing).

##### Where to go next?

- nFPM is a satellite project from GoReleaser. [Check it out](https://goreleaser.com)!
- Find examples and commented usage of all options in our [website](https://nfpm.goreleaser.com/).
- Reach out on [Discord](https://discord.gg/RGEBtg8vQ6) and [Twitter](https://twitter.com/goreleaser)!

<a href="https://goreleaser.com"><img src="https://raw.githubusercontent.com/goreleaser/artwork/master/opencollective-header.png" with="100%" alt="GoReleaser logo"></a>

</details>

<details>
<summary>rabbitmq/ra (ra)</summary>

### [`v3.1.9`](https://github.com/rabbitmq/ra/releases/tag/v3.1.9)

[Compare Source](rabbitmq/ra@v3.1.8...v3.1.9)

#### What's Changed

- ci: temporary fix for windows-latest changed by [@&#8203;lshir](https://github.com/lshir) in [#&#8203;639](rabbitmq/ra#639)
- Forward follower's append\_entries\_reply when it already has the snapshot by [@&#8203;kjnilsson](https://github.com/kjnilsson) in [#&#8203;641](rabbitmq/ra#641)
- Fix stale `last_written`/`pending` state after log truncation, and a snapshot-send regression by [@&#8203;kjnilsson](https://github.com/kjnilsson) in [#&#8203;644](rabbitmq/ra#644)
- Fix `force_shrink_members_to_current_member/1` typespec by [@&#8203;visciang](https://github.com/visciang) in [#&#8203;640](rabbitmq/ra#640)

**Full Changelog**: <rabbitmq/ra@v3.1.8...v3.1.9>

</details>

<details>
<summary>wojtekmach/req (req)</summary>

### [`v0.6.3`](https://github.com/wojtekmach/req/blob/HEAD/CHANGELOG.md#v063-2026-07-16)

[Compare Source](wojtekmach/req@v0.6.2...v0.6.3)

- \[`Req.Test`]: Fix race condition

</details>

<details>
<summary>rust-lang/rust (rust)</summary>

### [`v1.97.1`](https://github.com/rust-lang/rust/blob/HEAD/RELEASES.md#Version-1971-2026-07-16)

[Compare Source](rust-lang/rust@1.97.0...1.97.1)

\==========================

<a id="1.97.1"></a>

- [rustc: Fix miscompilation in LLVM optimization](rust-lang/rust#159035)
  This backports an LLVM submodule bump to include the LLVM-side fix and a
  revert of the rustc change that is one known trigger for the bug. The rustc
  side revert should not be strictly necessary but is done out of abundance of caution.

### [`v1.97.0`](https://github.com/rust-lang/rust/blob/HEAD/RELEASES.md#Version-1970-2026-07-09)

[Compare Source](rust-lang/rust@1.96.1...1.97.0)

\==========================

<a id="1.97.0-Language"></a>

## Language

- [Consider `Result<T, Uninhabited>` and `ControlFlow<Uninhabited, T>` to be equivalent to `T` for must use lint](rust-lang/rust#148214)
- [Add allow-by-default `dead_code_pub_in_binary` lint for unused pub items in binary crates](rust-lang/rust#149509)
- [Stabilize the `div32`, `lam-bh`, `lamcas`, `ld-seq-sa` and `scq` target features](rust-lang/rust#154510)
- [Stabilize `cfg(target_has_atomic_primitive_alignment)`](rust-lang/rust#155006)
- [Allow trailing `self` in imports in more cases](rust-lang/rust#155137)

<a id="1.97.0-Platform-Support"></a>

## Platform Support

- [nvptx64-nvidia-cuda: drop support for old architectures and old ISAs](rust-lang/rust#152443)

Refer to Rust's [platform support page][platform-support-doc]
for more information on Rust's tiered platform support.

[platform-support-doc]: https://doc.rust-lang.org/rustc/platform-support.html

<a id="1.97.0-Stabilized-APIs"></a>

## Stabilized APIs

- [`Default for RepeatN`](https://doc.rust-lang.org/stable/std/iter/struct.RepeatN.html#impl-Default-for-RepeatN%3CA%3E)
- [`Copy for ffi::FromBytesUntilNulError`](https://doc.rust-lang.org/stable/std/ffi/struct.FromBytesUntilNulError.html#impl-Copy-for-FromBytesUntilNulError)
- [`Send for std::fs::File` on UEFI](rust-lang/rust#154003)
- [`<{integer}>::isolate_highest_one`](https://doc.rust-lang.org/stable/std/primitive.u32.html#method.isolate_highest_one)
- [`<{integer}>::isolate_lowest_one`](https://doc.rust-lang.org/stable/std/primitive.u32.html#method.isolate_lowest_one)
- [`<{integer}>::highest_one`](https://doc.rust-lang.org/stable/std/primitive.u32.html#method.highest_one)
- [`<{integer}>::lowest_one`](https://doc.rust-lang.org/stable/std/primitive.u32.html#method.lowest_one)
- [`<{integer}>::bit_width`](https://doc.rust-lang.org/stable/std/primitive.u32.html#method.bit_width)
- [`NonZero<{integer}>::isolate_highest_one`](https://doc.rust-lang.org/stable/std/num/struct.NonZero.html#method.isolate_highest_one)
- [`NonZero<{integer}>::isolate_lowest_one`](https://doc.rust-lang.org/stable/std/num/struct.NonZero.html#method.isolate_lowest_one)
- [`NonZero<{integer}>::highest_one`](https://doc.rust-lang.org/stable/std/num/struct.NonZero.html#method.highest_one)
- [`NonZero<{integer}>::lowest_one`](https://doc.rust-lang.org/stable/std/num/struct.NonZero.html#method.lowest_one)
- [`NonZero<{integer}>::bit_width`](https://doc.rust-lang.org/stable/std/num/struct.NonZero.html#method.bit_width)

These previously stable APIs are now stable in const contexts:

- [`char::is_control`](https://doc.rust-lang.org/stable/std/primitive.char.html#method.is_control)

<a id="1.97.0-Cargo"></a>

## Cargo

- [Stabilize `build.warnings` config.](rust-lang/cargo#16796) This controls how lint warnings from local packages are treated. Useful for enforcing a warning-free build in CI, replacing `-Dwarnings`. [docs](https://doc.rust-lang.org/nightly/cargo/reference/config.html#buildwarnings)
- [Stabilize `resolver.lockfile-path` config.](rust-lang/cargo#16694) This allows specifying the path to the lockfile to use when resolving dependencies. Useful when working with read-only source directories. [docs](https://doc.rust-lang.org/nightly/cargo/reference/config.html#resolverlockfile-path)
- [cargo-clean: Error when `--target-dir` doesn't look like a Cargo target directory.](rust-lang/cargo#16712) This prevents accidental deletion of non-target directories.
- [Add `-m` shorthand for `--manifest-path`](rust-lang/cargo#16858)
- [Remove `curl` dependency from `crates-io` crate](rust-lang/cargo#16936)

<a id="1.97.0-Rustdoc"></a>

## Rustdoc

- [Stabilize `--emit` flag](rust-lang/rust#146220)
- [Stabilize `--remap-path-prefix`](rust-lang/rust#155307)

<a id="1.97.0-Compatibility-Notes"></a>

## Compatibility Notes

- [Emit a future-compatibility warning when relying on `f32: From<{float}>` to constrain `{float}`](rust-lang/rust#139087)
- [Rust will use the v0 symbol mangling scheme by default.](rust-lang/rust#151994) This may cause some tools (such as debuggers or profilers, especially with old versions) to fail to demangle symbols emitted by Rust. It may also cause the formatting of text in backtraces to change.
- [Prevent deref coercions in `pin!`, in order to prevent unsoundness.](rust-lang/rust#153457) The most likely case where this might impact users is: writing `pin!(x)` where `x` has type `&mut T` will now always correctly produce a value of type `Pin<&mut &mut T>`, instead of sometimes allowing a coercion that produces a value of type `Pin<&mut T>`. This coercion was previously incorrectly allowed since Rust 1.88.0.
- [Deprecate `std::char` constants and functions](rust-lang/rust#153873)
- [Warn on linker output by default](rust-lang/rust#153968)
- [Remove hidden `f64` methods which have been deprecated since 1.0](rust-lang/rust#153975)
- [report the `varargs_without_pattern` lint in deps](rust-lang/rust#154599)
- [Forbid passing generic arguments to module path segments even if the module reexports a generic enum variant](rust-lang/rust#154971)
- [Error on invalid macho `link_section` specifier](rust-lang/rust#155065)
- The encoding of certain `enum`s [have changed](rust-lang/rust#155473).  This is not a breaking change, as it only applies to `enum`s without layout guarantees, but is noted here as we've seen people impacted from having made assumptions about the layout algorithm.
- [Error on `#[export_name = "..."]` where the name is empty](rust-lang/rust#155515)
- [Syntactically reject tuple index shorthands in struct patterns](rust-lang/rust#155698)
- [validate `#[link_name = "..."]` & `#[link(name = "...")]` parameters](rust-lang/rust#155817)
- On Windows, after calling `shutdown` on a socket to shut down the write side, attempting to write to the socket will now produce a `BrokenPipe` error rather than `Other`. [Map `WSAESHUTDOWN` to `io::ErrorKind::BrokenPipe`](rust-lang/rust#156063)

### [`v1.96.1`](https://github.com/rust-lang/rust/blob/HEAD/RELEASES.md#Version-1961-2026-06-30)

[Compare Source](rust-lang/rust@1.96.0...1.96.1)

\===========================

<a id="1.96.1"></a>

- [Cargo: fix timeout/retry behavior](rust-lang/cargo#17131)
- [Cargo: apply patches for CVE-2025-15661, CVE-2026-55199, and CVE-2026-55200 to libssh2](rust-lang/cargo#17140)
- [rustc: fix miscompilation in MIR optimization](rust-lang/rust#158214)

</details>

<details>
<summary>serde-rs/serde (serde)</summary>

### [`v1.0.229`](https://github.com/serde-rs/serde/releases/tag/v1.0.229)

[Compare Source](serde-rs/serde@v1.0.228...v1.0.229)

- Update to syn 3

</details>

<details>
<summary>whatyouhide/stream_data (stream_data)</summary>

### [`v1.4.0`](https://github.com/whatyouhide/stream_data/blob/HEAD/CHANGELOG.md#v140)

[Compare Source](whatyouhide/stream_data@v1.3.0...v1.4.0)

- Require Elixir 1.14+.
  - Fix `StreamData.float/1` when min and max are too far apart.
  - Support choosing between graphemes and codepoints in `StreamData.string/2`.
  - Shrink `StreamData.one_of/1` towards earlier elements first (instead of smaller values for later elements).

</details>

<details>
<summary>dtolnay/thiserror (thiserror)</summary>

### [`v2.0.19`](https://github.com/dtolnay/thiserror/releases/tag/2.0.19)

[Compare Source](dtolnay/thiserror@2.0.18...2.0.19)

- Update to syn 3

</details>

---

### Configuration

📅 **Schedule**: (in timezone Pacific/Auckland)

- Branch creation
  - Between 12:00 AM and 03:59 AM, only on Monday (`* 0-3 * * 1`)
- Automerge
  - Between 12:00 AM and 03:59 AM (`* 0-3 * * *`)

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yNTUuMiIsInVwZGF0ZWRJblZlciI6IjQzLjI1NS4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZSJdfQ==-->

Co-authored-by: James Harton <james@harton.dev>
Reviewed-on: https://harton.dev/project-neon/neonfs/pulls/1568
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-attributes Area: Attributes (`#[…]`, `#![…]`) disposition-merge This issue / PR is in PFCP or FCP with a disposition to merge it. finished-final-comment-period The final comment period is finished for this PR / Issue. I-lang-radar Items that are on lang's radar and will need eventual work or consideration. relnotes Marks issues that should be documented in the release notes of the next release. S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-lang Relevant to the language team to-announce Announce this issue on triage meeting

Projects

None yet

Development

Successfully merging this pull request may close these issues.

llvm error: export_name

7 participants