Changes in main.yml

b7c30d11 - Add "GC Zeal" infrastructure for additional, aggressive GC assertions (#12921)

Wed, 01 Apr 2026 20:08:02 +0000

Add "GC Zeal" infrastructure for additional, aggressive GC assertions (#12921)* Add "GC Zeal" infrastructure for additional, aggressive GC assertionsThis initial commit just sets up the initial GC Zeal infrastructure, it doesn'tactually start using it anywhere yet.* Adds support for `cfg(gc_zeal)` to `crates/wasmtime/build.rs` and `crates/cranelift/build.rs`* Defines `gc_assert!` macro* Defines `wasmtime_environ::gc::POISON` constant for GC heap poisoning* Adds debug assert that `POISON` doesn't overlap any valid `VMGcKind` discriminant* Adds CI job to run GC-related tests with `cfg(gc_zeal)`* Review feedback List of files: /wasmtime-44.0.1/.github/workflows/main.yml

bc6585e8 - Fix logic and double-drop UB in `WriteBuffer` impls (#12870)

Mon, 30 Mar 2026 14:08:48 +0000

Fix logic and double-drop UB in `WriteBuffer` impls (#12870)For component-model-async this fixes logic and undefined behavior issuesin the implementation of the `WriteBuffer` trait for various types.Notably all types didn't respect the `unsafe` contract of the`WriteBuffer::take` method by limiting the number of results to what wasrequested. This flawed detail, when coupled with other implementationdetails, led to both incorrect results and UB in the case that`VecBuffer` was used where `T` had a `Drop` implementation. This isnot a security issue because component-model-async is not yet Tier 1 andthus is exempt from the security issue process, but this is nonethelesssomething needed to be fixed. List of files: /wasmtime-44.0.1/.github/workflows/main.yml

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/.github/workflows/main.yml

856fb272 - Debugging: add integration test with LLDB and some minor tweaks. (#12856)

Fri, 27 Mar 2026 19:38:06 +0000

Debugging: add integration test with LLDB and some minor tweaks. (#12856)This PR adds:- An integration-test that runs LLDB against the Wasmtime CLI to verify basic debugging functionality, similar to the existing native-debug tests.- A CI job that runs the above in CI.- Some minor tweaks to the gdbstub debugger design: - Rather than the initial single-step to get to the first Wasm instruction where module(s) will be instantiated into the store and visible to the debugger, we pre-register modules with the store eagerly. This avoids the slightly hacky flow and also is a preparation step for `wasmtime serve` debugging, where we can't single-step into execution eagerly (because execution doesn't start at all until an HTTP request arrives). - Add a separate message-printing path for "debugger info messages", allowing us to print the "debugger is listening on " message without inheriting stderr for the whole debugger component environment. This message is necessary for the above integration test (it parses the message to determine when the debuggee is ready). List of files: /wasmtime-44.0.1/.github/workflows/main.yml

0e51666b - CI: Add a check for cranelift-codegen (only x86 and aarch64) on no_std tagets (#12812)

Tue, 24 Mar 2026 20:57:57 +0000

CI: Add a check for cranelift-codegen (only x86 and aarch64) on no_std tagets (#12812)* CI: Add a check for cranelift-codegen (only x86 and aarch64) on no_std tagets* Change -F to --features* Fix CI: remove unused imports when building without unwind* Cargo fmt List of files: /wasmtime-44.0.1/.github/workflows/main.yml

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/.github/workflows/main.yml

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/.github/workflows/main.yml

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/.github/workflows/main.yml

819391b9 - Update more github actions (#12775)

Fri, 13 Mar 2026 17:31:36 +0000

Update more github actions (#12775)Missed in the prior update... List of files: /wasmtime-44.0.1/.github/workflows/main.yml

7cca98e5 - Update some github actions versions (#12762)

Wed, 11 Mar 2026 19:46:02 +0000

Update some github actions versions (#12762)CI is warning us about these, so try updating. List of files: /wasmtime-44.0.1/.github/workflows/main.yml

365e2d89 - Refactor WASIp2 `wasi:http` implementation (#12748)

Tue, 10 Mar 2026 16:24:22 +0000

Refactor WASIp2 `wasi:http` implementation (#12748)* Sequester WASIp2 in `wasmtime-wasi-http` to a moduleThis mirrors the `wasmtime-wasi` crate's organization where there's a`p2` module and a `p3` module at the top level.* Refactor WASIp2 `wasi:http` implementationThis commit reorganizes and refactors the WASIp2 implementation of`wasi:http` to look more like other `wasmtime-wasi`-style interfaces.Specifically the old `WasiHttpImpl` structure is removed in favor ofas `WasiHttpCtxView<'_>` type that is used to implementbindgen-generated `Host` traits. This necessitated reorganizing themethods of the previous `WasiHttpView` trait like so:* The `WasiHttpView` trait is renamed to `WasiHttpHooks` to make space for a new `WasiHttpView` which behaves like `WasiView`, for example.* The `ctx` and `table` methods of `WasiHttpHooks` were removed since they'll be fields in `WasiHttpCtxView`.* Helper methods for WASIp2 were moved to methods on `WasiHttpCtxView` instead of default methods on `WasiHttpHooks`.With these changes in place the WASIp3 organization was also updatedslightly as well. Notably WASIp3 now contains a reference to the crate's`WasiHttpCtx` structure (which has field limits for example). WASIp3'sprevious `WasiHttpCtx` trait is now renamed to `WasiHttpHooks` as well.This means that there are two `WasiHttpHooks` traits right now, one forWASIp2 and one for WASIp3. In the future I would like to unify these twobut that will require some more work around the default `send_request`.A final note here is that the `WasiHttpHooks` trait previously, andcontinues to be, optional for embedders to implement. Default functionsare provided as `wasmtime_wasi_http::{p2, p3}::default_hooks`.Additionally there's a `Default for &mut dyn WasiHttpHooks`implementation, too.With all that outlined: the motivation for this change is to bring theWASIp2 and WASIp3 implementations of `wasi:http` closer together. Thisis inspired by refactorings I was doing for #12674 to apply the sameheader limitations for WASIp3 as is done for WASIp2. Prior to thischange there were a number of differences such as WASIp3 not having`crate::WasiHttpCtx` around, WASIp2 having a different organization ofstructures/borrows, etc. The goal is to bring the two implementationscloser in line with each other to make refactoring across them moreconsistent and easier.* Make `WasiHttp` in WASIp2 public* Fix some conditional build* Fix some doctests* Fix configured build* Fixup documentation List of files: /wasmtime-44.0.1/.github/workflows/main.yml

7746998d - Allow using `demangle` feature in `no_std` builds. (#12740)

Mon, 09 Mar 2026 16:12:38 +0000

Allow using `demangle` feature in `no_std` builds. (#12740)While there, add `async`, `debug`, `debug-builtins` and `anyhow` tothe list of features supporting `#![no_std]`, and update the CI jobto include those features.Signed-off-by: Piotr Sikora List of files: /wasmtime-44.0.1/.github/workflows/main.yml

bda02c19 - chore: bump to wasi 0.3.0-rc-2026-02-09 (#12557)

Fri, 13 Feb 2026 20:22:31 +0000

chore: bump to wasi 0.3.0-rc-2026-02-09 (#12557) List of files: /wasmtime-44.0.1/.github/workflows/main.yml

232fd3cf - Update to wasi-sdk-30 in CI (#12495)

Wed, 04 Feb 2026 16:26:12 +0000

Update to wasi-sdk-30 in CI (#12495)Testing it out and keeping it up-to-dateprtest:full List of files: /wasmtime-44.0.1/.github/workflows/main.yml

621d7ebb - Switch back to emulation of s390x tests (#12491)

Tue, 03 Feb 2026 00:57:50 +0000

Switch back to emulation of s390x tests (#12491)* Switch back to emulation of s390x testsRecent changes looks like it's triggering some sort of bug to cancel allour workflows without actually running anything. Avoid the s390x runnersfor now.* Pin wkg used in CI List of files: /wasmtime-44.0.1/.github/workflows/main.yml

47e1cd59 - fix: skip importing `std::path::Path` regardless of `cache` feature (#12479)

Fri, 30 Jan 2026 19:47:02 +0000

fix: skip importing `std::path::Path` regardless of `cache` feature (#12479)Signed-off-by: Ho Kim List of files: /wasmtime-44.0.1/.github/workflows/main.yml

d0f49441 - Pin fuzz build in CI to oss-fuzz's Rust version (#12459)

Wed, 28 Jan 2026 15:54:21 +0000

Pin fuzz build in CI to oss-fuzz's Rust version (#12459)We updated our MSRV recently and that broke the build on OSS-Fuzz. Toavoid this happening again set things up in CI to ensure that thisdoesn't happen again without informing us we should update OSS-Fuzzfirst. List of files: /wasmtime-44.0.1/.github/workflows/main.yml

bc4582c3 - Forbid rustdoc warnings in CI (#12420)

Tue, 27 Jan 2026 03:47:35 +0000

Forbid rustdoc warnings in CI (#12420)* Forbid rustdoc warnings in CIThis commit corrects our handling of rustdoc flags in CI to ensure thatwarnings indeed fire. Additionally this changes our flags to pass`-Dwarnings` to ensure that we have warning-free doc builds when allfeatures are enabled at least.There were quite a lot of preexisting issues to fix, so thisadditionally goes through and fixes all the warnings that cropped up.* Update nightly toolchain againprtest:full* Update another nightly* Fix a warning in generated code List of files: /wasmtime-44.0.1/.github/workflows/main.yml

8325e1ec - Fold the `wasmtime-error` crate into `wasmtime-core` (#12418)

Fri, 23 Jan 2026 23:32:22 +0000

Fold the `wasmtime-error` crate into `wasmtime-core` (#12418)Similar to #12398 and #12407 the idea is that all our dependency-free(mostly) data structures and foundational data-types are in one locationto centralize testing, ergonomics, documentation, idioms, etc. List of files: /wasmtime-44.0.1/.github/workflows/main.yml

9acefdfe - Merge `wasmtime-math` into `wasmtime-core` (#12398)

Fri, 23 Jan 2026 16:53:02 +0000

Merge `wasmtime-math` into `wasmtime-core` (#12398)* Merge `wasmtime-math` into `wasmtime-core`No real need to have two "core" crates, let's just have one.* Fix warnings List of files: /wasmtime-44.0.1/.github/workflows/main.yml