build(deps): bump the all-deps group with 2 updates

[dependabot]

Bumps the all-deps group with 2 updates: cfg-if and getrandom.

Updates cfg-if from 1.0.3 to 1.0.4

Release notes

Sourced from cfg-if's releases.

v1.0.4

• Support cfg(true) and cfg(false) (#99)
• Set and test a MSRV of 1.32
• Have a single top-level rule

Changelog

Sourced from cfg-if's changelog.

1.0.4 - 2025-10-15

• Support cfg(true) and cfg(false) (#99)
• Set and test a MSRV of 1.32
• Have a single top-level rule

Commits

• 3510ca6 chore: release v1.0.4 (#95)
• 15aec4a Support cfg(true) and cfg(false) (#99)
• 036c64e Set and test a MSRV of 1.32
• 5fd566f Set -Dwarnings via CI env rather than cfg
• 8ef8e9f Have a single top-level rule.
• 2400b38 Document and test for a subtle case.
• See full diff in compare view

Updates getrandom from 0.3.3 to 0.3.4

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

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Looks like these dependencies are no longer updatable, so this is no longer needed.