Release Version v0.3.4 (rust-random#735)

## [0.3.4] - 2025-10-14

### Major change to `wasm_js` backend

Now, when the `wasm_js` feature is enabled, the `wasm_js` backend will
be used
by default. Users of `wasm32-unknown-unknown` targeting JavaScript
environments
like the Web and Node.js will no longer need to specify:
```
--cfg getrandom_backend="wasm_js"
```
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
of
randomness _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 [rust-random#671], [rust-random#675], and [rust-random#730].

### Added
- `unsupported` opt-in backend [rust-random#667]
- `windows_legacy` opt-in backend [rust-random#724]

### Changed
- Implement Memory Sanitizer unpoisoning more precisely [rust-random#678]
- Relax MSRV for the `linux_raw` opt-in backend on ARM targets [rust-random#688]
- Use `getrandom` syscall on all RISC-V Linux targets [rust-random#699]
- Replaced `wasi` dependency with `wasip2` [rust-random#721]
- Enable `wasm_js` backend by default if the `wasm_js` feature is
enabled [rust-random#730]

### Removed
- Unstable `rustc-dep-of-std` crate feature [rust-random#694]

[rust-random#667]: rust-random#667
[rust-random#671]: rust-random#671
[rust-random#675]: rust-random#675
[rust-random#678]: rust-random#678
[rust-random#688]: rust-random#688
[rust-random#694]: rust-random#694
[rust-random#699]: rust-random#699
[rust-random#721]: rust-random#721
[rust-random#724]: rust-random#724
[rust-random#730]: rust-random#730

---------

Signed-off-by: Joe Richey <joerichey@google.com>

Author: josephlr

CHANGELOG.md

@@ -4,7 +4,24 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [0.3.4] - UNRELEASED
+## [0.3.4] - 2025-10-14
+
+### Major change to `wasm_js` backend
+
+Now, when the `wasm_js` feature is enabled, the `wasm_js` backend will be used
+by default. Users of `wasm32-unknown-unknown` targeting JavaScript environments
+like the Web and Node.js will no longer need to specify:
+```
+--cfg getrandom_backend="wasm_js"
+```
+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 of
+randomness _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 [#667]
@@ -15,25 +32,29 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Relax MSRV for the `linux_raw` opt-in backend on ARM targets [#688]
 - Use `getrandom` syscall on all RISC-V Linux targets [#699]
 - Replaced `wasi` dependency with `wasip2` [#721]
+- Enable `wasm_js` backend by default if the `wasm_js` feature is enabled [#730]
 
 ### Removed
 - Unstable `rustc-dep-of-std` crate feature [#694]
 
 [#667]: https://github.com/rust-random/getrandom/pull/667
+[#671]: https://github.com/rust-random/getrandom/issues/671
+[#675]: https://github.com/rust-random/getrandom/pull/675
 [#678]: https://github.com/rust-random/getrandom/pull/678
 [#688]: https://github.com/rust-random/getrandom/pull/688
 [#694]: https://github.com/rust-random/getrandom/pull/694
 [#699]: https://github.com/rust-random/getrandom/pull/699
 [#721]: https://github.com/rust-random/getrandom/pull/721
 [#724]: https://github.com/rust-random/getrandom/pull/724
+[#730]: https://github.com/rust-random/getrandom/pull/730
 
 ## [0.3.3] - 2025-05-09
 
 ### Changed
 - Doc improvements [#632] [#634] [#635]
 - Add crate version to docs.rs links used in `compile_error!`s [#639]
 
-## Fixed
+### Fixed
 - Error handling in WASI p1 [#661]
 
 [#632]: https://github.com/rust-random/getrandom/pull/632

README.md

@@ -84,7 +84,7 @@ of randomness based on their specific needs:
 | `linux_raw`       | Linux, Android       | `*‑linux‑*`              | Same as `linux_getrandom`, but uses raw `asm!`-based syscalls instead of `libc`.
 | `rdrand`          | x86, x86-64          | `x86_64-*`, `i686-*`     | [`RDRAND`] instruction
 | `rndr`            | AArch64              | `aarch64-*`              | [`RNDR`] register
-| `wasm_js`         | Web Browser, Node.js | `wasm32‑unknown‑unknown`, `wasm32v1-none` | [`Crypto.getRandomValues`]. Requires feature `wasm_js` ([see below](#webassembly-support)).
+| `wasm_js`         | Web Browser, Node.js | `wasm32‑unknown‑unknown`, `wasm32v1-none` | [`Crypto.getRandomValues`]. Enabled by the `wasm_js` feature ([see below](#webassembly-support)).
 | `efi_rng`         | UEFI                 | `*-unknown‑uefi`         | [`EFI_RNG_PROTOCOL`] with `EFI_RNG_ALGORITHM_RAW` (requires `std` and Nightly compiler)
 | `windows_legacy`  | Windows              | `*-windows-*`            | [`RtlGenRandom`]
 | `custom`          | All targets          | `*`                      | User-provided custom implementation (see [custom backend])
@@ -138,8 +138,9 @@ requires [`wasm-bindgen`], **bloating `Cargo.lock`** and
 
 To enable `getrandom`'s functionality on `wasm32-unknown-unknown` using the Web
 Crypto methods [described above][opt-in] via [`wasm-bindgen`], enable the
-`wasm_js` feature flag. Optionally, one can also set
-`RUSTFLAGS='--cfg getrandom_backend="wasm_js"'`.
+`wasm_js` feature flag. Setting `RUSTFLAGS='--cfg getrandom_backend="wasm_js"'`
+is allowed but is no longer required and does nothing (it was required in a
+prior version of this crate).
 
 WARNING: enabling the `wasm_js` feature will bloat `Cargo.lock` on all platforms
 (where [`wasm-bindgen`] is not an existing dependency) and is known to cause

build.rs

@@ -34,8 +34,8 @@ fn main() {
     // Automatically detect cfg(sanitize = "memory") even if cfg(sanitize) isn't
     // supported. Build scripts get cfg() info, even if the cfg is unstable.
     println!("cargo:rerun-if-changed=build.rs");
-    let santizers = std::env::var("CARGO_CFG_SANITIZE").unwrap_or_default();
-    if santizers.contains("memory") {
+    let sanitizers = std::env::var("CARGO_CFG_SANITIZE").unwrap_or_default();
+    if sanitizers.contains("memory") {
         println!("cargo:rustc-cfg=getrandom_msan");
     }