chore: upgrades Rust version and dependencies#651
Merged
Conversation
thadouk
force-pushed
the
chore/switch-to-rust-stable-1.67-wasm32v1
branch
from
04891b8 to
8c6a757
Compare
fluorostani
approved these changes
Jan 29, 2026
micaelffrancoAV
approved these changes
Jan 29, 2026
Changes toolchain and CI to use Rust 1.87.0 Additionally, drops wasm-unknown-unknown dependency in favour of `wasm32v1-none` to align with polkadot-sdk feature: feat(wasm-builder): add support for new `wasm32v1-none` target polkadot-sdk PR: [#7008](paritytech/polkadot-sdk#7008) Resolves [#5777](paritytech/polkadot-sdk#5777) Previously `wasm-builder` used hacks such as `-Zbuild-std` (required `rust-src` component) and `RUSTC_BOOTSTRAP=1` to build WASM runtime without WASM features: `sign-ext`, `multivalue` and `reference-types`, but since Rust 1.84 (will be stable on 9 January, 2025) the situation has improved as there is new [`wasm32v1-none`](https://doc.rust-lang.org/beta/rustc/platform-support/wasm32v1-none.html) target that disables all "post-MVP" WASM features except `mutable-globals`. Wasm builder requires the following prerequisites for building the WASM binary: - Rust >= 1.68 and Rust < 1.84: - `wasm32-unknown-unknown` target - `rust-src` component - Rust >= 1.84: - `wasm32v1-none` target - no more `-Zbuild-std` and `RUSTC_BOOTSTRAP=1` hacks and `rust-src` component requirements! Jira: - SYS-4677 - SYS-4551
thadouk
force-pushed
the
chore/switch-to-rust-stable-1.67-wasm32v1
branch
from
8c6a757 to
b7d3ba3
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Proposed changes
Additionally, drops wasm-unknown-unknown dependency in favour of
wasm32v1-noneto align with polkadot-sdk feature:feat(wasm-builder): add support for new
wasm32v1-nonetarget polkadot-sdk PR: #7008 Resolves #5777Previously
wasm-builderused hacks such as-Zbuild-std(requiredrust-srccomponent) andRUSTC_BOOTSTRAP=1to build WASM runtime without WASM features:sign-ext,multivalueandreference-types, but since Rust 1.84 (will be stable on 9 January, 2025) the situation has improved as there is newwasm32v1-nonetarget that disables all "post-MVP" WASM features exceptmutable-globals.Wasm builder requires the following prerequisites for building the WASM binary:
wasm32-unknown-unknowntargetrust-srccomponentwasm32v1-nonetarget-Zbuild-stdandRUSTC_BOOTSTRAP=1hacks andrust-srccomponent requirements!Jira:
Type of change/Merge
🚨What type of change is this PR?
Put an
xin the boxes that apply