fix(repo): install nightly Rust for WASM build in publish workflow #33792
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The mise migration removed the pre-installed nightly Rust toolchain that was available on ubuntu-latest runners. The WASM build requires nightly Rust because it uses the unstable `wasi_ext` feature. Changes: - Add explicit `rustup toolchain install nightly-2025-12-10` before WASM build - Update build:wasm script from old nightly-2025-05-09 to nightly-2025-12-10 This ensures the nightly toolchain is available before the build script attempts to use it via `rustup override set`.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
✅ Deploy Preview for nx-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
View your CI Pipeline Execution ↗ for commit c37d913
☁️ Nx Cloud last updated this comment at |
jaysoo
approved these changes
Dec 10, 2025
FrozenPandaz
added a commit
that referenced
this pull request
Dec 15, 2025
…33792) ## Current Behavior After the mise migration (#33772), the `publish.yml` workflow fails during the "Build Wasm" step with: ``` error[E0554]: `#![feature]` may not be used on the stable release channel --> packages/nx/src/lib.rs:2:33 | 2 | #![cfg_attr(target_os = "wasi", feature(wasi_ext))] ``` The WASM build requires nightly Rust because it uses the unstable `wasi_ext` feature. The `build:wasm` script attempts to switch to nightly via `rustup override set`, but after the mise migration, the nightly toolchain is no longer pre-installed, causing the build to fail with the stable compiler. ## Expected Behavior The WASM build should successfully compile using nightly Rust with the `wasi_ext` feature. ## Related Issue(s) Fixes the publish workflow regression introduced in #33772
Contributor
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current Behavior
After the mise migration (#33772), the
publish.ymlworkflow fails during the "Build Wasm" step with:The WASM build requires nightly Rust because it uses the unstable
wasi_extfeature. Thebuild:wasmscript attempts to switch to nightly viarustup override set, but after the mise migration, the nightly toolchain is no longer pre-installed, causing the build to fail with the stable compiler.Expected Behavior
The WASM build should successfully compile using nightly Rust with the
wasi_extfeature.Related Issue(s)
Fixes the publish workflow regression introduced in #33772