chore(deps): bump the cargo group across 1 directory with 3 updates

[dependabot]

Bumps the cargo group with 3 updates in the / directory: wasmtime, rand and rustls-webpki.

Updates wasmtime from 43.0.0 to 44.0.0

Release notes

Sourced from wasmtime's releases.

v44.0.0

44.0.0

Released 2026-04-20.

Added

• The wasmtime CLI now supports a -g flag which runs a built-in wasm program to host a gdbstub-compatible server (can be connected to with LLDB) to debug guest programs. #12756 #12771 #12856 #12859

• Wasmtime now has experimental support for the map<K, V> type in the component model. #12216

• Wasmtime's C API now supports wasm tag types. #12763 #12803

• Wasmtime's C API now supports exceptions. #12861

• Wasmtime's C API has more support for the GC proposal. #12914 #12915 #12916 #12917

• An initial implementation of the wasi:tls proposal for the 0.3.0-draft version has been added. #12834

Changed

• The demangle Cargo feature of the wasmtime crate is now compatible with no_std targets. #12740

• The wasmtime-wasi-tls-* crates are now merged into one crate with feature flags for each backend. #12780

• Wasmtime now requires Rust 1.92.0 or later to build. #12828

• The cranelift-codegen crate now compiles for no_std targets.

... (truncated)

Changelog

Sourced from wasmtime's changelog.

45.0.0

Unreleased.

Added

Changed

---

Release notes for previous releases of Wasmtime can be found on the respective release branches of the Wasmtime repository.

• 44.0.x
• 43.0.x
• 42.0.x
• 41.0.x
• 40.0.x
• 39.0.x
• 38.0.x
• 37.0.x
• 36.0.x
• 35.0.x
• 34.0.x
• 33.0.x
• 32.0.x
• 31.0.x
• 30.0.x
• 29.0.x
• 28.0.x
• 27.0.x
• 26.0.x
• 25.0.x
• 24.0.x
• 23.0.x
• 22.0.x
• 21.0.x
• 20.0.x
• 19.0.x
• 18.0.x
• 17.0.x
• 16.0.x
• 15.0.x
• 14.0.x
• 13.0.x
• 12.0.x
• 11.0.x
• 10.0.x
• 9.0.x

... (truncated)

Commits

• af382d7 Release Wasmtime 44.0.0 (#13143)
• 272d1b1 Add release notes (#13096)
• 39e910b [44.0.0] Merged backports for security advisories (#13007)
• eb4c527 Fix another panic optimizing vector expressions (#12961)
• 122ddc7 Handle OOM in Func::call_async and fiber creation (#12954)
• 7088e01 Update GC proposal status in docs (#12918)
• 1e73c1f Fix panic optimizing vector expressions (#12957)
• 0126a94 Add anyref downcast methods to the C and C++ APIs (#12917)
• 5c68fe6 Add support for async tests to our OOM test infrastructure (#12953)
• fc8dc5d Add support for arrayrefs to the C and C++ APIs (#12916)
• Additional commits viewable in compare view

Updates rand from 0.8.5 to 0.8.6

Changelog

Sourced from rand's changelog.

[0.8.6] - 2026-04-14

This release back-ports a fix from v0.10. See also #1763.

Changes

• Deprecate feature log (#1772)

#1763: rust-random/rand#1763 #1772: rust-random/rand#1772

• Drop the experimental simd_support feature.

Commits

• 5309f25 0.8.6 (#1772): update for recent nightly rustc and backport #1764
• 1126d03 When testing rustc 1.36, use compatible dependencies.
• 143b602 Add Cargo.lock.msrv.
• 9be86f2 Fix cross build test.
• 5e0d50d Drop simd_support.
• 8ff02f0 Upgrade cache action.
• 4ad0cc3 Don't test for unsupported target architecture.
• 258e6d0 Address warning.
• 9f0e676 Mark some internal traits as potentially unused.
• 6f123c1 Workaround never constructed and never used warning.
• Additional commits viewable in compare view

Updates rustls-webpki from 0.103.10 to 0.103.13

Release notes

Sourced from rustls-webpki's releases.

0.103.13

• Fix reachable panic in parsing a CRL. This was reported to us as GHSA-82j2-j2ch-gfr8. Users who don't use CRLs are not affected.
• For name constraints on URI names, we incorrectly processed excluded subtrees in a way which inverted the desired meaning. See rustls/webpki#471. This was a case missing in the fix for GHSA-965h-392x-2mh5.

What's Changed

• Actually fail closed for URI matching against excluded subtrees by @​djc in rustls/webpki#473
• Prepare 0.103.13 by @​ctz in rustls/webpki#474

Full Changelog: rustls/webpki@v/0.103.12...v/0.103.13

0.103.12

This release fixes two bugs in name constraint enforcement:

• GHSA-965h-392x-2mh5: name constraints for URI names were ignored and therefore accepted. URI name constraints are now rejected unconditionally. Note this library does not provide an API for asserting URI names, and URI name constraints are otherwise not implemented.
• GHSA-xgp8-3hg3-c2mh: permitted subtree name constraints for DNS names were accepted for certificates asserting a wildcard name. This was incorrect because, given a name constraint of accept.example.com, *.example.com could feasibly allow a name of reject.example.com which is outside the constraint. This is very similar to CVE-2025-61727.

Since name constraints are restrictions on otherwise properly-issued certificates, these bugs are reachable only after signature verification and require misissuance to exploit.

What's Changed

• Prepare 0.103.12 by @​djc in rustls/webpki#470

Full Changelog: rustls/webpki@v/0.103.11...v/0.103.12

0.103.11

In response to #464, we've slightly relaxed requirements for anchor_from_trust_cert() to ignore unknown extensions even if they're marked as critical. This only affects parsing a TrustAnchor from DER, for which most extensions are ignored anyway.

What's Changed

• Backport parsing trust anchors with unknown critical extensions to 0.103 by @​djc in rustls/webpki#466

Commits

• 2879b2c Prepare 0.103.13
• 2c49773 Improve tests for padding of BitStringFlags
• 4e3c0b3 Correct validation of BIT STRING constraints
• 39c91d2 Actually fail closed for URI matching against excluded subtrees
• 27131d4 Bump version to 0.103.12
• 6ecb876 Clean up stuttery enum variant names
• 318b3e6 Ignore wildcard labels when matching name constraints
• 1219622 Rewrite constraint matching to avoid permissive catch-all branch
• 57bc62c Bump version to 0.103.11
• d0fa01e Allow parsing trust anchors with unknown criticial extensions
• See full diff 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 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
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: af27e2e0bc

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Align Wasmtime companion crate majors

Bumping only wasmtime to 44 while keeping wasmtime-wasi* on 43 introduces two incompatible wasmtime major versions in the workspace (Cargo.lock shows wasmtime-wasi 43 depends on wasmtime 43.0.0), which breaks crates that use both APIs together, e.g. crates/imagod-runtime-wasmtime/src/plugin_resolver.rs builds a wasmtime::component::Linker and passes it to wasmtime_wasi::p2::add_to_linker_async. Those functions require the Linker type from the same major version, so this mixed-version update is expected to cause type-mismatch build failures for runtime/plugin components.

Useful? React with 👍 / 👎.