chore(deps): bump the wasmtime-dependencies group across 1 directory with 3 updates

[dependabot]

Bumps the wasmtime-dependencies group with 3 updates in the / directory: wasmtime, wasmtime-wasi and deterministic-wasi-ctx.

Updates wasmtime from 39.0.1 to 41.0.4

Release notes

Sourced from wasmtime's releases.

v41.0.4

41.0.4

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

• Panic when dropping a [Typed]Func::call_async future. GHSA-xjhv-v822-pf94

v41.0.3

41.0.3

Released 2026-02-04.

Fixed

• Fix an incorrect mid-end optimization rule that could cause a compiler panic due to mismatched types. #12504

v41.0.2

41.0.2

Released 2026-02-03.

Fixed

• Reduce the dependencies of the wasmtime-internal-jit-icache-coherence crate. #12446

v41.0.1

... (truncated)

Changelog

Sourced from wasmtime's changelog.

41.0.4

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

• Panic when dropping a [Typed]Func::call_async future. GHSA-xjhv-v822-pf94

---

41.0.3

Released 2026-02-04.

Fixed

• Fix an incorrect mid-end optimization rule that could cause a compiler panic due to mismatched types. #12504

---

41.0.2

Released 2026-02-03.

Fixed

• Reduce the dependencies of the wasmtime-internal-jit-icache-coherence crate. #12446

... (truncated)

Commits

• d938a9d Release Wasmtime 41.0.4 (#12654)
• d86b007 [41.0.x] Backport fixes for security advisories (#12650)
• db1c043 Release Wasmtime 41.0.3 (#12529)
• 604f64b [41.0] Backport Cranelift: mid-end: fix constant types in some icmp/select ru...
• 881e9a3 Release Wasmtime 41.0.2 (#12499)
• 1f6bc69 Revert "Release Wasmtime 41.0.2 (#12487)" (#12494)
• 3a65814 Switch back to emulation of s390x tests (#12492)
• 67e082f Release Wasmtime 41.0.2 (#12487)
• 2ca28e6 Directly use anyhow rather than wasmtime-environ in wasmtime-jit-icache-coher...
• c30fce8 Release Wasmtime 41.0.1 (#12434)
• Additional commits viewable in compare view

Updates wasmtime-wasi from 39.0.1 to 41.0.4

Release notes

Sourced from wasmtime-wasi's releases.

v41.0.4

41.0.4

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

• Panic when dropping a [Typed]Func::call_async future. GHSA-xjhv-v822-pf94

v41.0.3

41.0.3

Released 2026-02-04.

Fixed

• Fix an incorrect mid-end optimization rule that could cause a compiler panic due to mismatched types. #12504

v41.0.2

41.0.2

Released 2026-02-03.

Fixed

• Reduce the dependencies of the wasmtime-internal-jit-icache-coherence crate. #12446

v41.0.1

... (truncated)

Changelog

Sourced from wasmtime-wasi's changelog.

41.0.4

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

• Panic when dropping a [Typed]Func::call_async future. GHSA-xjhv-v822-pf94

---

41.0.3

Released 2026-02-04.

Fixed

• Fix an incorrect mid-end optimization rule that could cause a compiler panic due to mismatched types. #12504

---

41.0.2

Released 2026-02-03.

Fixed

• Reduce the dependencies of the wasmtime-internal-jit-icache-coherence crate. #12446

... (truncated)

Commits

• d938a9d Release Wasmtime 41.0.4 (#12654)
• d86b007 [41.0.x] Backport fixes for security advisories (#12650)
• db1c043 Release Wasmtime 41.0.3 (#12529)
• 604f64b [41.0] Backport Cranelift: mid-end: fix constant types in some icmp/select ru...
• 881e9a3 Release Wasmtime 41.0.2 (#12499)
• 1f6bc69 Revert "Release Wasmtime 41.0.2 (#12487)" (#12494)
• 3a65814 Switch back to emulation of s390x tests (#12492)
• 67e082f Release Wasmtime 41.0.2 (#12487)
• 2ca28e6 Directly use anyhow rather than wasmtime-environ in wasmtime-jit-icache-coher...
• c30fce8 Release Wasmtime 41.0.1 (#12434)
• Additional commits viewable in compare view

Updates deterministic-wasi-ctx from 3.0.4 to 3.0.6

Release notes

Sourced from deterministic-wasi-ctx's releases.

v3.0.6

What's Changed

• Bump actions/checkout from 3.6.0 to 6.0.1 by @​dependabot[bot] in Shopify/deterministic-wasi-ctx#121
• Bump actions/cache from 3.4.3 to 5.0.1 by @​dependabot[bot] in Shopify/deterministic-wasi-ctx#122
• Update to Wasmtime 40 by @​jeffcharles in Shopify/deterministic-wasi-ctx#123
• v3.0.5 by @​jeffcharles in Shopify/deterministic-wasi-ctx#124
• Update to Wasmtime 41 by @​jeffcharles in Shopify/deterministic-wasi-ctx#126
• v3.0.6 by @​jeffcharles in Shopify/deterministic-wasi-ctx#127

Full Changelog: Shopify/deterministic-wasi-ctx@v3.0.4...v3.0.6

Commits

• d191a8d v3.0.6 (#127)
• 94e7bab Update to Wasmtime 41 (#126)
• ba98321 v3.0.5 (#124)
• 967e4c4 Update to Wasmtime 40 (#123)
• f1d55f9 Bump actions/cache from 3.4.3 to 5.0.1 (#122)
• 688a19c Bump actions/checkout from 3.6.0 to 6.0.1 (#121)
• See full diff in compare view