Skip to content

dist(release/1.29): backport patches#4867

Draft
rami3l wants to merge 37 commits into
rust-lang:release/1.29from
rami3l:backport/202605
Draft

dist(release/1.29): backport patches#4867
rami3l wants to merge 37 commits into
rust-lang:release/1.29from
rami3l:backport/202605

Conversation

@rami3l
Copy link
Copy Markdown
Member

@rami3l rami3l commented May 23, 2026

Warning

This is an experimentation of how backporting could possibly work. Don't merge yet.

@djc wow, with atomic commits, backporting is as simple as dropping the incompatible commits? I'm impressed...

@rami3l rami3l added the backport This is an issue which should be backported to the next patch release, or it is a backporting PR. label May 23, 2026
@rami3l rami3l force-pushed the backport/202605 branch from ca510c1 to 4c152f4 Compare May 23, 2026 18:05
@rami3l rami3l force-pushed the backport/202605 branch from 4c152f4 to c4dbaf4 Compare May 23, 2026 18:14
@rami3l
Copy link
Copy Markdown
Member Author

rami3l commented May 23, 2026

Well, there ARE some rough edges but should be pretty simple to resolve, I'll find some time to look at them later... At least there has been 0 conflicts during the rebase which is quite impressive in itself already :o

rami3l and others added 11 commits May 23, 2026 20:37
…g "unchanged"


When the v2 channel manifest's `.toml` did not match its published `.sha256`, `try_update_from_dist_` mapped `RustupError::ChecksumFailed` to `Ok(None)`. Callers interpret `Ok(None)` as "no update available", so `rustup update` printed only a `warn:` line, reported the toolchain as `unchanged`, and exited 0, even though the manifest could not be
integrity-checked.
…_RECURSION_COUNT`

This commit clears the value of `RUSTUP_AUTO_INSTALL` and the
`RUST_RECURSION_COUNT` environment variables before running tests, to
make sure that every test case relying on their effects is explicitly
setting them.
@rami3l rami3l force-pushed the backport/202605 branch from c4dbaf4 to 84dc4f3 Compare May 23, 2026 18:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This is an issue which should be backported to the next patch release, or it is a backporting PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants