Skip to content

Upgrade Rust toolchain to nightly-2026-04-14#557

Open
github-actions[bot] wants to merge 1 commit intomainfrom
rust-toolchain-upgrade
Open

Upgrade Rust toolchain to nightly-2026-04-14#557
github-actions[bot] wants to merge 1 commit intomainfrom
rust-toolchain-upgrade

Conversation

@github-actions
Copy link
Copy Markdown

@github-actions github-actions bot commented Apr 13, 2026

This PR upgrades the Rust toolchain to the latest available nightly version.

Changes

  • Updated rust-toolchain.toml to use nightly-2026-04-14
  • Updated commit hash to 17584a181979f04f2aaad867332c22db1caa511a
  • Updated REQUIRED_RUST_TOOLCHAIN in crates/rustc_codegen_spirv/build.rs

Verification

  • All required components are available
  • Project builds successfully
  • Tests pass

This PR was automatically generated by the Rust toolchain upgrade workflow.

Copy link
Copy Markdown
Member

@Firestar99 Firestar99 left a comment

Choose a reason for hiding this comment

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

We're gonna delay merging this in favor of staying on nightly-2026-04-11, which is the branch date of rustc 1.96.0, in #563

@nazar-pc
Copy link
Copy Markdown
Contributor

Why does it matter where stable branches off?

@Firestar99
Copy link
Copy Markdown
Member

Mainly this: #545 (comment)

@LegNeato
Copy link
Copy Markdown
Collaborator

Only for the release, right? After that we move forward?

Updates:
- rust-toolchain.toml: nightly-2026-04-14
- commit hash: 17584a181979f04f2aaad867332c22db1caa511a
- REQUIRED_RUST_TOOLCHAIN in build.rs
@github-actions github-actions bot changed the title Upgrade Rust toolchain to nightly-2026-04-13 Upgrade Rust toolchain to nightly-2026-04-14 Apr 14, 2026
@github-actions github-actions bot force-pushed the rust-toolchain-upgrade branch from 62bf623 to 68e70a9 Compare April 14, 2026 04:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants