chore(deps): bump wasmtime from 27.0.0 to 36.0.6 in the cargo group across 1 directory

[dependabot]

Bumps the cargo group with 1 update in the / directory: wasmtime.

Updates wasmtime from 27.0.0 to 36.0.6

Release notes

Sourced from wasmtime's releases.

v36.0.6

36.0.6

Released 2026-02-24.

Changed

• Wasmtime's implementation of WASI now has the ability to limit resource consumption on behalf of the guest, such as host-allocated memory. This means that some behaviors previously allowed by Wasmtime can now disallowed, such as transferring excessive data from the guest to the host. Additionally calls to wasi:random/random.get-random-bytes, for example, can have limits in place to avoid allocating too much memory on the host. To preserve backwards-compatible behavior these limits are NOT set by default. Embedders must opt-in to configuring these knobs as appropriate for their embeddings. For more information on this see the related security advisory with further details on knobs added and what behaviors can be restricted. GHSA-852m-cvvp-9p4w

Fixed

• Panics when adding too many headers to a wasi:http/types.fields has been resolved GHSA-243v-98vx-264h

v36.0.5

36.0.5

Released 2026-01-26.

Fixed

• Fixed a bug in lowering of f64.copysign on x86-64 whereby when combined with an f64.load, the resulting machine code could read 16 bytes rather than 8 bytes. This could result in a segfault when Wasmtime is configured without signals-based traps.

v36.0.4

36.0.4

Released 2026-01-14.

Fixed

• A possible stack overflow in the x64 backend with cmp emission has been fixed. #12333

v36.0.3

36.0.3

... (truncated)

Changelog

Sourced from wasmtime's changelog.

36.0.6

Released 2026-02-24.

Changed

• Wasmtime's implementation of WASI now has the ability to limit resource consumption on behalf of the guest, such as host-allocated memory. This means that some behaviors previously allowed by Wasmtime can now disallowed, such as transferring excessive data from the guest to the host. Additionally calls to wasi:random/random.get-random-bytes, for example, can have limits in place to avoid allocating too much memory on the host. To preserve backwards-compatible behavior these limits are NOT set by default. Embedders must opt-in to configuring these knobs as appropriate for their embeddings. For more information on this see the related security advisory with further details on knobs added and what behaviors can be restricted. GHSA-852m-cvvp-9p4w

Fixed

• Panics when adding too many headers to a wasi:http/types.fields has been resolved GHSA-243v-98vx-264h

---

36.0.5

Released 2026-01-26.

Fixed

• Fixed a bug in lowering of f64.copysign on x86-64 whereby when combined with an f64.load, the resulting machine code could read 16 bytes rather than 8 bytes. This could result in a segfault when Wasmtime is configured without signals-based traps.

---

36.0.4

Released 2026-01-14.

Fixed

• A possible stack overflow in the x64 backend with cmp emission has been fixed. #12333

---

... (truncated)

Commits

• f2054e0 Release Wasmtime 36.0.6 (#12656)
• 48b427b [36.0.x] Backport fixes for security advisories (#12648)
• 06ef143 Release Wasmtime 36.0.5 (#12432)
• ac92d9b [36.0] Backport Cranelift: x64: fix incorrect load-sinking in copysign oper...
• 0489f91 Release Wasmtime 36.0.4 (#12348)
• 5c1a5f6 Cranelift: x64: fix user-controlled recursion in cmp emission. (#12333) (#12338)
• 8c97ae8 Migrate this workspace to using trusted publishing (#12257) (#12280)
• 17d037f Release Wasmtime 36.0.3 (#12023)
• 9fe3f5f [36.0.x] Prevent using shared memories with Memory (#12018)
• f554fa9 [36.0.x] Use github immutable releases (#11916)
• Additional commits viewable in compare view

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

[dependabot]

Looks like wasmtime is no longer updatable, so this is no longer needed.