chore(deps): update rust crate getrandom to 0.3

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
getrandom	workspace.dependencies	minor	0.2 → 0.3

---

Release Notes

rust-random/getrandom (getrandom)

v0.3.4

Compare Source

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

v0.3.3

Compare Source

Changed

• Doc improvements #​632 #​634 #​635
• Add crate version to docs.rs links used in compile_error!s #​639

Fixed

• Error handling in WASI p1 #​661

v0.3.2

Compare Source

Added

• efi_rng opt-in backend #​570
• linux_raw opt-in backend #​572
• .cargo/config.toml example in the crate-level docs #​591
• getrandom_test_linux_without_fallback configuration flag to test that file fallback
  is not triggered in the linux_android_with_fallback backend #​605
• Built-in support for *-linux-none targets #​618
• Cygwin support #​626

Changed

• Update wasi dependency to v0.14 #​594
• Add #[inline] attribute to the inner functions #​596
• Update WASI and Emscripten links in the crate-level docs #​597
• Do not use dlsym on MUSL targets in the linux_android_with_fallback backend #​602
• Remove linux_android.rs and use getrandom.rs instead #​603
• Always use RtlGenRandom on Windows targets when compiling with pre-1.78 Rust #​610
• Internal representation of the Error type #​614
• Remove windows-targets dependency and use raw-dylib directly #​627

Removed

• Error::INTERNAL_START and Error::CUSTOM_START associated constants #​614

v0.3.1

Compare Source

Fixed

• Build error on Android #​588

v0.3.0

Compare Source

Breaking Changes

Changed

• Bump MSRV to 1.63 #​542
• Rename getrandom and getrandom_uninit functions to fill and fill_uninit respectively #​532

Removed

• wasm32-wasi target support (use wasm32-wasip1 or wasm32-wasip2 instead) #​499
• linux_disable_fallback, rdrand, js, test-in-browser, and custom crate features
  in favor of configuration flags #​504
• register_custom_getrandom! macro #​504
• Implementation of From<NonZeroU32> for Error and Error::code method #​507
• Internet Explorer 11 support #​554
• Target-specific associated Error constants #​562

Changed

• Use ProcessPrng on Windows 10 and up, and use RtlGenRandom on older Windows versions #​415
• Do not use locale-specific strerror_r for retrieving error code descriptions #​440
• Avoid assuming usize is the native word size in the rdrand backend #​442
• Do not read from errno when libc did not indicate error on Solaris #​448
• Switch from libpthread's mutex to futex on Linux and to nanosleep-based wait loop
  on other targets in the use_file backend #​490
• Do not retry on EAGAIN while polling /dev/random on Linux #​522
• Remove separate codepath for Node.js in the wasm_js backend
  (bumps minimum supported Node.js version to v19) #​557
• Use js_namespace in the wasm_js backend #​559

Added

• wasm32-wasip1 and wasm32-wasip2 support #​499
• getrandom_backend configuration flag for selection of opt-in backends #​504
• Error::new_custom method #​507
• rndr opt-in backend #​512
• Automatic MemorySanitizer support #​521 #​571
• u32 and u64 functions for generating random values of the respective type #​544
• wasm32v1-none support in the wasm_js backend #​560
• wasm_js crate feature which allows users to enable the wasm_js opt-in backend #​574

Fixed

• NetBSD fallback code based on KERN_ARND #​555

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package getrandom@0.2.16 --precise 0.3.4
    Updating crates.io index
error: failed to select a version for the requirement `getrandom = "^0.2"`
candidate versions found which didn't match: 0.3.4
location searched: crates.io index
required by package `sequoia-openpgp v2.1.0`
    ... which satisfies dependency `sequoia-openpgp = "^2"` (locked to 2.1.0) of package `pdf-sign-gpg v0.2.0 (/tmp/renovate/repos/github/0x77dev/pdf-sign/crates/gpg)`

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}