Changes in Cargo.lock

f302ebd6 - Release Wasmtime 44.0.1 (#13241)

Thu, 30 Apr 2026 15:36:47 +0000

Release Wasmtime 44.0.1 (#13241)[automatically-tag-and-release-this-commit]Co-authored-by: Wasmtime Publish List of files: /wasmtime-44.0.1/Cargo.lock

122ddc71 - Handle OOM in `Func::call_async` and fiber creation (#12954)

Fri, 03 Apr 2026 20:17:49 +0000

Handle OOM in `Func::call_async` and fiber creation (#12954)* Handle OOM in `Func::call_async` and fiber creation* fix clippy* fix build* really fix build* address review feedback* fix build* fix warnings List of files: /wasmtime-44.0.1/Cargo.lock

e4305755 - Add wasi:http support to the C API (#12950)

Fri, 03 Apr 2026 16:41:51 +0000

Add wasi:http support to the C API (#12950) List of files: /wasmtime-44.0.1/Cargo.lock

e9e1665c - Update `mutatis` dep to 0.4.0 (#12945)

Fri, 03 Apr 2026 13:37:15 +0000

Update `mutatis` dep to 0.4.0 (#12945) List of files: /wasmtime-44.0.1/Cargo.lock

46780983 - Exceptions: add exception-specific (command-sequence) fuzzer. (#12923)

Wed, 01 Apr 2026 22:26:11 +0000

Exceptions: add exception-specific (command-sequence) fuzzer. (#12923)* Exceptions: add exception-specific (command-sequence) fuzzer.This fuzzer uses a description of a set of "scenarios", arbitrarilygenerated, to produce a specific kind of module that tests throw/catchbehavior. The module contains a chain of functions that invoke eachother; one will throw, and the rest may have catch clauses that do ordo not catch.* Review feedback. List of files: /wasmtime-44.0.1/Cargo.lock

da36d99d - Update wasm-tools dependencies (#12920)

Tue, 31 Mar 2026 23:52:24 +0000

Update wasm-tools dependencies (#12920)Pull in the latest updates with some minor fixes, too. List of files: /wasmtime-44.0.1/Cargo.lock

694e553b - feat(p3): implement wasi:tls (#12834)

Mon, 30 Mar 2026 13:46:29 +0000

feat(p3): implement wasi:tls (#12834)* Split off p2-specific bits into submodule* Vendor the 0.3.0-draft WIT files* Host traits scaffolding* Rename p2 test* Work around bug in `tokio-native-tls`* Create error type* Implement p3Co-authored-by: Roman Volosatovs * Fix test on Windows' SChannelSame reason as described in https://github.com/bytecodealliance/wasmtime/pull/11064* Satisfy clippy* Fix typo---------Co-authored-by: Roman Volosatovs List of files: /wasmtime-44.0.1/Cargo.lock

a2cc11f3 - Update object to 0.39.0 (#12866)

Mon, 30 Mar 2026 09:35:59 +0000

Update object to 0.39.0 (#12866)* Update object to 0.39.0* Add vets for `object`---------Co-authored-by: Alex Crichton List of files: /wasmtime-44.0.1/Cargo.lock

6ce71e92 - Update `tokio-rustls` to 0.26.4, `rustls` to 0.23 (#12837)

Thu, 26 Mar 2026 21:40:07 +0000

Update `tokio-rustls` to 0.26.4, `rustls` to 0.23 (#12837)* Update `tokio-rustls` to 0.26.4, `rustls` to 0.23This updates `rustls-webpki` from 0.102.x, which is vulnerable toincorrect CRL distribution point matching (RUSTSEC-2026-0049),to 0.103.10. Uses `ring` as the crypto backend to preserve existingdependencies.* cargo vets for update to rustlsWe had previously exempted rustls, rustls-webpki, and tokio-rustls fromvetting. The exempted versions have been updated.We were able to pull in a vet from mozilla for zeroize, which hadpreviously been exempted. I audited the (small) diff from the importedaudit version.---------Co-authored-by: Pat Hickey List of files: /wasmtime-44.0.1/Cargo.lock

9ed377c0 - update `tar` dep (#12835)

Tue, 24 Mar 2026 23:56:45 +0000

update `tar` dep (#12835)* update tar* cargo vet prunes these entries List of files: /wasmtime-44.0.1/Cargo.lock

dbaaa92f - Debugging: add builtin gdbstub component. (#12771)

Tue, 24 Mar 2026 18:27:01 +0000

Debugging: add builtin gdbstub component. (#12771)* Debugging: add builtin gdbstub component.This adds a debug component that makes use of the debug-main worlddefined in #12756 and serves the gdbstub protocol, with Wasmextensions, compatible with LLDB.This component is built and included inside the Wasmtime binary, andis loaded using the lower-level `-D debugger=...` debug-main option;the user doesn't need to specify the `.wasm` adaptercomponent. Instead, the user simply runs `wasmtime run -g program.wasm ...` and Wasmtime will load and prepare to run`program.wasm` as the debuggee, waiting for a gdbstub connection onthe given TCP port before continuing.The workflow is:```$ wasmtime run -g 1234 program.wasm[ wasmtime starts and waits for connection ]$ /opt/wasi-sdk/bin/lldb # use LLDB from wasi-sdk release 32 or later(lldb) process connect --plugin wasm connect://localhost:1234Process 1 stopped* thread #1, stop reason = signal SIGTRAP frame #0: 0x40000000000001cc-> 0x40000000000001cc: unreachable 0x40000000000001cd: end 0x40000000000001ce: local.get 0 0x40000000000001d0: call 13(lldb) siProcess 1 stopped* thread #1, stop reason = instruction step into frame #0: 0x4000000000000184-> 0x4000000000000184: block 0x4000000000000186: block 0x4000000000000188: global.get 1 0x400000000000018e: i32.const 3664[ ... ]```This makes use of the `gdbstub` third-party crate, into which I'veupstreamed support for the Wasm extensions in daniel5151/gdbstub#188,daniel5151/gdbstub#189, daniel5151/gdbstub#190, anddaniel5151/gdbstub#192. (I'll add vets as part of this PR.)* cargo vets.* Handle Trap events as well as breakpoints.* Review feedback.* Fix gdbstub artifact build to make it publishable (by disabling it when isolated crates are used).* Review feedback.* fix published-crates list* For now, empty gdbstub data but no compile error when artifact crate is published.* add some more Cargo metadata: version for artifact crate dep List of files: /wasmtime-44.0.1/Cargo.lock

134d56e7 - Merge the wasi-tls crates into a single one with feature flags (#12780)

Mon, 16 Mar 2026 15:39:54 +0000

Merge the wasi-tls crates into a single one with feature flags (#12780)prtest:full List of files: /wasmtime-44.0.1/Cargo.lock

133a0ef4 - Debugging: add the debug-main world. (#12756)

Fri, 13 Mar 2026 18:58:17 +0000

Debugging: add the debug-main world. (#12756)* Debugging: add the debug-main world.This PR "draws the rest of the owl" for the debug-mainworld (bytecodealliance/rfcs#45). This includes a WIT world that hostsdebug components that have access to "host debug powers" via adebugging API, and the ability to load such a debug-component and giveit control of the main program as a debuggee when using `wasmtimerun`.The WIT is namespaced to `bytecodealliance:wasmtime` and is slightlyaspirational in places: for example, the host does not yet implementinjection of early return values or exception-throws. I intend to fillout a series of TODO issues once this all lands to track followup("post-MVP") work.This PR does not include any debug components. I separately have agdbstub component, with which I tested and co-developed this host-sideimplementation. My plan is to land it in a followup PR as a componentthat will be embedded in/shipped with the Wasmtime CLI and availableunder an easy-to-use CLI option. Once we have that gdbstub component,we can also implement end-to-end integration tests that boot up LLDBand run through an expected interaction. (Separately, thoseintegration tests will require a release of wasi-sdk to ship an LLDBbinary that we can use.) As such, there are no real tests in this PR:interesting behaviors only really occur with a full end-to-end flow.The integration with the CLI is a little awkward (we internally buildanother `wasmtime run` command that invokes the debug component, andtie it together with the debuggee via a special `invoke_debugger` API;this seemed less bad than reworking all of the WASI setup to be morereusable). Happy to take more ideas here.* Review feedback.* Review feedback.* Review feedback: update vendor-wit.sh.* Review feedback: -Ddebugger-arg= -> -Darg=.* Review feedback.* Review feedback.* Review feedback: factor host.rs into several submodules.* Review feedback: rename Debugger to Debuggee on host side.* Review feedback: split inherit_stdin_stdout, and add corresponding options for the debug component.* Review feedback.* Review feedback.* Add simple debug-component tests.* Add wasm32-wasip2 target in a few places in CI* Cargo vets for wstd dependency.* Add wasm32-wasip2 in more places* fix debug-component test dependence on componentization byte offsets* Review feedback.* Fix cancel-safety of EventFuture.* Fix: Interrupted events should only occur after interrupt(), not on every epoch yield.* Review feedback.* Review feedback: strip down WASI imports in debugger world.* fold debugger test component back into wasip1 + adapter test artifact compilation flow List of files: /wasmtime-44.0.1/Cargo.lock

c5ab9e5a - Bump Wasmtime to 44.0.0 (#12728)

Thu, 05 Mar 2026 15:31:51 +0000

Bump Wasmtime to 44.0.0 (#12728)Co-authored-by: Wasmtime Publish List of files: /wasmtime-44.0.1/Cargo.lock

bb3de558 - Add an OOM-handling `BTreeMap` implementation (#12712)

Wed, 04 Mar 2026 19:10:34 +0000

Add an OOM-handling `BTreeMap` implementation (#12712)* Add an OOM-handling `BTreeMap` implementation* review feedback* fix docs links List of files: /wasmtime-44.0.1/Cargo.lock

550a07c3 - Add insertion methods with fallible allocation to `cranelift_bforest::{Map,Set}` (#12685)

Mon, 02 Mar 2026 21:24:01 +0000

Add insertion methods with fallible allocation to `cranelift_bforest::{Map,Set}` (#12685) List of files: /wasmtime-44.0.1/Cargo.lock

f85e4d09 - Add a microbenchmark for compile-time builtins (#12660)

Wed, 25 Feb 2026 15:51:30 +0000

Add a microbenchmark for compile-time builtins (#12660) List of files: /wasmtime-44.0.1/Cargo.lock

bbfcd588 - deps: Update `bumpalo` to version 3.20.0 (#12614)

Wed, 18 Feb 2026 16:44:02 +0000

deps: Update `bumpalo` to version 3.20.0 (#12614) List of files: /wasmtime-44.0.1/Cargo.lock

b5d2ff5d - Cranelift: update regalloc2 to 0.15.0 to permit more VRegs. (#12611)

Wed, 18 Feb 2026 00:23:43 +0000

Cranelift: update regalloc2 to 0.15.0 to permit more VRegs. (#12611)* Cranelift: update regalloc2 to 0.15.0 to permit more VRegs.This pulls in bytecodealliance/regalloc2#257 to permit more VRegs tobe used in a single function body, addressing #12229 and our followupdiscussions about supporting function body sizes up to the Wasmimplementation limit standard.In addition to the RA2 upgrade, this also includes a bit more explicitlimit-checking on the Cranelift side: note that we don't directly use`regalloc2::VReg` but instead we further bitpack it into `Reg`, whichis logically a sum type of `VReg`, `PReg` and `SpillSlot` (the lastone needed to represent stack allocation locations on defs, e.g. oncallsites with many returns). `PReg`s are packed into the beginning ofthe `VReg` index space but `SpillSlot`s are distinguished by stealingthe upper bit of a `u32`. This was previously not a problem given thesmaller `VReg` index space but now we need to check explicitly; hence`Reg::from_virtual_reg_checked` and its use in the lowering vregallocator. Because the `VReg` index packs the class into the bottomtwo bits, and index into the upper 30, but we steal one bit at thetop, the true limit for VReg count is thus actually 2^29, or512M.Fixes #12229.* Drop `code_too_large` test. List of files: /wasmtime-44.0.1/Cargo.lock

df579907 - Cranelift: upgrade to regalloc2 0.14.0 and use static/constant `MachineEnv`s. (#12596)

Sun, 15 Feb 2026 01:51:20 +0000

Cranelift: upgrade to regalloc2 0.14.0 and use static/constant `MachineEnv`s. (#12596)* Update to new regalloc2 with constant MachineEnv.* Re-bless Cranelift filetests.* Re-bless Wasmtime disas tests.* Update to RA2 0.14.0.* Review feedback.* cargo-vet update. List of files: /wasmtime-44.0.1/Cargo.lock