deps(deps): update getrandom requirement from 0.2 to 0.3

[dependabot]

Updates the requirements on getrandom to permit the latest version.

Release notes

Sourced from getrandom's releases.

getrandom v0.3.4

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
• windows_legacy opt-in backend #724

Changed

• Implement Memory Sanitizer unpoisoning more precisely #678
• 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: rust-random/getrandom#667 #671: rust-random/getrandom#671 #675: rust-random/getrandom#675 #678: rust-random/getrandom#678 #688: rust-random/getrandom#688 #694: rust-random/getrandom#694 #699: rust-random/getrandom#699 #721: rust-random/getrandom#721 #724: rust-random/getrandom#724 #730: rust-random/getrandom#730

Changelog

Sourced from getrandom's changelog.

[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
• windows_legacy opt-in backend #724

Changed

• Implement Memory Sanitizer unpoisoning more precisely #678
• 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: rust-random/getrandom#667 #671: rust-random/getrandom#671 #675: rust-random/getrandom#675 #678: rust-random/getrandom#678 #688: rust-random/getrandom#688 #694: rust-random/getrandom#694 #699: rust-random/getrandom#699 #721: rust-random/getrandom#721 #724: rust-random/getrandom#724 #730: rust-random/getrandom#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

... (truncated)

Commits

• 38e4ad3 Update version number to v0.3.4 (#736)
• 2d033b7 Release Version v0.3.4 (#735)
• ccb0ca9 build(deps): bump the all-deps group across 1 directory with 5 updates (#734)
• 1af2510 Implement #675: let wasm_js enable the backend by default (#730)
• 18d8984 Don't run doctests with -Zsanitizer=memory
• c904801 Change removed doc_auto_cfg feature
• d4cb6a2 Update all nightly toolchains to latest nightly
• 9b78fcc Update Cargo.lock (#731)
• b6ac385 ci: re-enable NetBSD job (#729)
• 3983e0f Add windows_legacy opt-in backend (#724)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: dependencies, rust. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.