Release Version v0.3.4 #735
Merged
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.
[0.3.4] - 2025-10-14
Major change to
wasm_js
backendNow, when the
wasm_js
feature is enabled, thewasm_js
backend will be usedby default. Users of
wasm32-unknown-unknown
targeting JavaScript environmentslike the Web and Node.js will no longer need to specify:
in
RUSTFLAGS
for the crate to compile. They can now simple enable a feature.Note: this should not affect non-JS users of the
wasm32-unknown-unknown
target. Using
--cfg getrandom_backend
will still override the source ofrandomness even if the
wasm_js
feature is enabled. This includes--cfg getrandom_backend=custom
and--cfg getrandom_backend=unsupported
.For more information, see the discussions in #671, #675, and #730.
Added
unsupported
opt-in backend #667windows_legacy
opt-in backend #724Changed
linux_raw
opt-in backend on ARM targets #688getrandom
syscall on all RISC-V Linux targets #699wasi
dependency withwasip2
#721wasm_js
backend by default if thewasm_js
feature is enabled #730Removed
rustc-dep-of-std
crate feature #694