NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io
crates.io, #3410 most downloaded on crates.io
INTERNAL: Uni-typed slab with a free list for use in Wasmtime
Latest stable
41.0.4
Last release 24 days ago
29 Oct 2026
Ships fairly regularly
a new release about every 3 weeks
Nearly every release is documented
notes for 43 of 44 stable releases
Nothing withdrawn
no release was ever pulled
1 years old
44 releases · first in 2025
Drag across the ruler to compare, or tap a release to open it.
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
Released 2026-02-24.
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-9p4wPanics 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
Fix an incorrect mid-end optimization rule that could cause a compiler panic due to mismatched types. #12504
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Released 2026-02-04.
Reduce the dependencies of the wasmtime-internal-jit-icache-coherence crate. #12446
Released 2026-02-03.
wasmtime-internal-jit-icache-coherence crate.
#12446Fixed 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
Released 2026-01-26.
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.Support for {Future,Stream}Any in the component model has improved. #12142
Released 2026-01-20.
Support for {Future,Stream}Any in the component model has improved.
#12142
Wasmtime has initial support for breakpoints and single-stepping with the
debug feature for guest programs.
#12133
Wasmtime has begun adding a new Error type which is similar to
anyhow::Error but supports gracefully handling OOM. Wasmtime still uses
anyhow::Error but this will change in the future to wasmtime::Error which
will be a distinct type.
#12163
An initial top-level crate for async-debugging guest programs has been added. #12183
Cranelift now optimizes redundant select + icmp instructions.
#12135
Synchronous component model functions can no longer block before returning.
This implements a change in the upstream specification to the upcoming async
support in the component model which places stricter restrictions on
non-async functions and their ability to perform blocking operations.
#12043
Frame iteration in debug mode now visits all activations which enables
seeing all frames from recursive wasm calls.
#12176
Wasmtime now requires Rust 1.90.0 or later. #12167
Intra-component stream/future reads/writes are now allowed for simple data types. #12181
The POLL callback code has been removed from the canonical ABI for async
functions and the waitable-set.poll function no longer yields.
#12182
Guest-to-guest adapters injected by Wasmtime now have improved trapping error messages. #12215
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
Released 2026-02-24.
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-9p4wPanics 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
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
Released 2026-01-26.
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.A possible stack overflow in the x64 backend with cmp emission has been fixed. #12333
This release is a test of Wasmtime's CI-based crate publishing infrastructure. Wasmtime is switching to crates.io-based trusted publishing for this re
Released 2026-01-07.
WASIp3 support for wasi:http now implements Response::from_http to convert from standard Rust types to WASI types. #12063
Released 2025-12-20.
WASIp3 support for wasi:http now implements Response::from_http to convert
from standard Rust types to WASI types.
#12063
Cranelift now supports a "patchable" ABI which has a maximum number of
arguments and clobbers no registers. This is paired as well with a new
patchable_call instruction which supports being turned into NOPs at runtime.
#12061
#12101
Support for the WebAssembly threads proposal is now classified as tier 2 by
default. Additionally creation of SharedMemory is disabled by deafult behind
a new config knob/CLI flag.
#12036
A variety of peephole-style optimizations have been added to Cranelift's optimization passes. #11994 #11995 #11996 #11997 #11998 #11999 #12000 #12006 #12008
Component host functions have been slightly optimized to remove an Arc clone
and reduce contention.
#11987
Support for component-model-async has been updated to account for the changes specified in WebAssembly/component-model#578. This means that historical binaries using WASIp3, for example, are no longer valid. Recompilation of historical components will be required and source-level changes may also be required in some circumstances. #12031 #12043
The UnsyncBoxBody type is now used everywhere in wasmtime-wasi-http instead
of just in the wasip3 support.
#12060
Initial groundwork for gracefully handling OOM (e.g. returning an error instead of aborting) has been added. #12070 #12089
Wasmtime will create a private copy of code memory when guest debugging is enabled to assist with modifying code when adding/removing breakpoints. #12051
The ResourceTable type will no longer use Tombstone when compiled in debug
mode.
#12114
Intra-component future/stream reads/writes will now trap instead of accidentally being allowed. #12117
Cranelift optimization rules have been tweaked after it was discovered that they could pessimize code containing long chains of computations. #12116
Compilation of i8x16.popcnt has been fixed in Winch for some potential
inputs.
#12010
A panic in Instance::prepare_call for some component-model-async situations
has been fixed.
#12054
An off-by-one error for lifting/lowering enums/variants with 255 cases has been fixed. #12066
Restarting the read of a host future after cancellation has been fixed. #12093
Compilation for OpenBSD on x86_64 has been fixed. #12097
Components containing a module type which exoprts a tag are now supported.
#12125
A possible stack overflow in the x64 backend with cmp emission has been fixed. #12333
Released 2026-01-14.
cmp emission has been
fixed.
#12333Compiling the debug feature without the gc feature enabled has been fixed. #12074
Released 2025-11-24.
debug feature without the gc feature enabled has been fixed.
#12074Initial work has begun to support WebAssembly-level debugging natively in Wasmtime. This is intended to complement today's preexisting DWARF-level deb
Released 2025-11-20.
Initial work has begun to support WebAssembly-level debugging natively in Wasmtime. This is intended to complement today's preexisting DWARF-level debugging, but this work will be portable and operate at the WebAssembly level of abstraction rather than the machine-level. Note that this work is not yet complete at this time but is expected to get filled out over the coming releases. #11768 #11769 #11873 #11892 #11895
The pooling allocator now exposes more metrics about unused slots. #11789
The Wizer and component-init projects have been merged into Wasmtime under
a new wasmtime wizer CLI subcommand and wasmtime-wizer crate. This is
mostly a drop-in replacement for both with a minor caveat that the
initialization function is now called wizer-initialize instead of
wizer.initialize to be compatible with components.
#11805
#11851
#11853
#11855
#11857
#11863
#11866
#11867
#11877
#11876
#11878
#11891
#11897
#11898
The Config::wasm_feature method is now public.
#11812
Enabling the wasm exceptions proposal is now exposed in the C API. #11861
The wasmtime crate now has a custom-sync-primitives Cargo feature which
enables using custom synchronization primitives defined by the embedder. This
is useful in no_std targets where the default panic-on-contention primitives
are not appropriate.
#11836
Wasmtime now supports unsafe intrinsics to be used for compile-time builtins. This can be used to provide give low-level access to host APIs/memory to a guest program in a controlled fashion. #11825 #11918
The signals_based_traps configuration option is now exposed in the C API.
#11879
A new EqRef::from_i31 function has been added.
#11884
The wasmtime serve subcommand will, by default, now reuse instances when
used with WASIp3 components. This increases throughput and additionally
showcases the concurrent features of WASIp3. This can be opted-out-of on the
CLI as well.
#11807
The C++ API for components has been filled out and implemented. #11880 #11889 #11988
A new ResourceDynamic type, similar to Resource<T>, has been added to
support host resources that have a dynamic tag at runtime rather than a
statically known tag at compile time. This is then used to implement resources
in the C/C++ API as well.
#11885
#11920
The C/C++ API of Wasmtime now supports the custom-page-sizes wasm proposal. #11890
Initial support has been added for the cooperative multithreading component model proposal in Wasmtime, built on async primitives. #11751
The epoch_deadline_callback Rust API has been bound in C++.
#11945
A new Request::into_http helper has been added to the WASIp3 implementation
of wasi:http.
#11843
A define_unknown_imports_as_traps function has been added to the C API.
#11962
A callback-based implementation of stdout and stderr has been added to the
C API for WASI configuration.
#11965
Running async functions in the component model now operates at the
Store-level of abstraction rather than an Instance.
#11796
The wasmtime serve subcommand no longer mistakenly spawns an epoch thread
per-request and instead uses a single epoch thread.
#11817
The component-model-async Cargo feature is now on-by-default. Note that it
is still gated at runtime by default. Also note that Wasmtime 39 does not include
#12031 which means
that components using async produced with the latest wasm-tools will not run
in Wasmtime 39. To run async components it's recommended to pin to a
historical version of wasm-tools and guest toolchains for now.
#11822
Bindings generated by wiggle no longer use async_trait.
#11839
Wasmtime's documentation now has an example of a plugin system using Wasmtime. #11848
Profiling with perfmap or jitdump now uses O_APPEND to be more amenable to
other engines in the same process also using perfmap/jitdump.
#11865
The wasmtime-wasi-http crate now uses UnsyncBoxBody to clarify that Sync
is not required.
#11941
A . character is now used instead of / int he bindgen! macro to separate
interface members.
#11947
The func_new function for component linkers now provides the type to the
callee so it knows the type that the component that imported it is using.
#11944
The component::Func type now has a type accessor and the old params/result
accessors were deleted.
#11943
Wasmtime now requires Rust 1.89.0 or later to compile. #11959
Some panics handling shapes of components with resources in various locations has been fixed. #11798
Bitwise float operations in Cranelift have been fixed on aarch64. #11811
An off-by-one in the bounds check of wasm atomic operations has been fixed. #11977
Bounds-check elision now happens again with 4 GiB guard pages. #11973
Prevent using shared memories with Memory. CVE-2025-64345
Fix possible host crash with host-to-wasm component intrinsics CVE-2025-62711
Released 2025-10-24.
This repository is attempting to start out using GitHub's "Immutable Releases" feature with this release, and this'll be the first release, assuming a
Released 2025-10-21.
Fixed some automation that went wrong with the 38.0.0 release.
Released 2025-10-20.
Nothing published for this version
Prevent using shared memories with Memory. CVE-2025-64345
Fix a memory leak in the C API when using anyref or externref. CVE-2025-61670.
Released 2025-10-07.
anyref or externref.
CVE-2025-61670.Cranelift's cranelift-jit crate now properly applies relocations to ADRP instructions on aarch64; a zero-extension on the offset was fixed to properly
Released 2025-09-23.
cranelift-jit crate now properly applies relocations to ADRP
instructions on aarch64; a zero-extension on the offset was fixed to properly
sign-extend instead.
#11734Wasmtime now fully implements the WebAssembly exception-handling proposal. Support is still disabled by default but is ready for testing. The proposal
Released 2025-09-20.
Wasmtime now fully implements the WebAssembly exception-handling proposal. Support is still disabled by default but is ready for testing. The proposal will be enabled by default in a future release of Wasmtime. #11326
An initial implementation of WASIp3 is available for the 0.3.0-rc-2025-08-15
tag made for the WASIp3 release. Note that this is not production ready yet
but is an excellent time to start kicking the tires in preparation for an
upcoming officialy WASIp3 0.3.0 release. Users of the CLI can opt-in with
-Sp3 -Wcomponent-model-async.
#11406
#11423
#11443
Wasmtime has initial support for the Linux PAGEMAP_SCAN ioctl which can
greatly improve instantiation throughput in scenarios with a high number of
instantiations and short instance lifetime. This support is disabled by
default but will likely be enabled by default in a future release.
#11372
#11433
GC support can now be configured in Config and not only through crate
features through Config::gc_support.
#11463
Wasmtime now supports reading metrics of the pooling allocator at runtime. #11490
The ManuallyRooted type is now replaced with OwnedRooted which is intended
to make management of GC object lifetimes on the host easier.
#11514
Wasmtime's documentation of the C++ embedding API and examples has been expanded. #11569
Wasmtime's support for the stack-switching WebAssembly proposal continues to progress on x86_64 Linux. #11003
The preview0 and preview1 modules and features in the wasmtime-wasi
crate are now called p0 and p1.
#11380
Release artifacts for the C API are now unconditionally built with unwind tables. #11383
Wasmtime now requires Rust 1.87.0 or later to build. #11396
The component-model-async gated AbortHandle is now named JoinHandle.
#11414
Wasmtime's internal implementation details are now async in many more
locations to help ensure the implementation is more sound.
#11411
#11416
#11442
#11444
#11457
#11460
#11461
#11468
#11470
#11481
#11496
Component-model-async primitives such as streams, tasks, etc, now use the same table as resources in a component. This means that guest-visible allocated indices are updated slightly. #11374
Wasmtime's precompiled binaries available from CI now include the
component-model-async feature.
#11429
C API release artifacts are now built with LTO so they have a smaller size. #11483
Code can no longer be loaded on x86_64-unknown-none by default without
opting-in to a contract that either the host is compiled with SSE2 support or
wasm is compiled with enough features that libcalls aren't used.
#11553
Host support for component model async futures/streams has been updated to a new API. #11515
GC of dead DWARF has been improved. #11402
Wasm-gc branching instructions now correctly check for fuel. #11426
The array.new_default instruction now checks for fuel/epochs in its inner
loop.
#11428
The "min" C API artifacts now have correct headers. #11479
GC OOM during const eval no longer panics. #11557
Wasmtime now properly respects a disabled std feature even on targets which
have std available.
#11568
Unchecked memory usage in transferring borrowed resources between components has been fixed. GHSA-6fr9-xmw9-5352
Released 2026-10-29.
Unchecked memory usage in transferring borrowed resources between components has been fixed. GHSA-6fr9-xmw9-5352
Fixed a possibility of content-length being invalid or not matching body length in wasi-http p2. GHSA-h4wp-g4x3-7398
v36.0.20: Release Wasmtime 36.0.20 (#15064)
Compare
wasi-http: Guests can add conflicting content lengths to messages GHSA-r8xh-cgf7-392j
Released 2026-10-19.
br_table instruction
GHSA-mghf-wjfp-p5xmv36.0.19: Release Wasmtime 36.0.19 (#14815)
Compare
Component-model handle tables are capped only per instance and charged to no limit. GHSA-q554-3cjc-rx7p
Released 2026-10-14.
Component-model handle tables are capped only per instance and charged to no limit. GHSA-q554-3cjc-rx7p
Filesystem sandbox escape when renaming symlinks with trailing slashes. GHSA-m9f7-9w4p-gv38
Guests can send absolute-form HTTP requests to different hosts. GHSA-5qpp-g3j2-8frx
v36.0.18: Release Wasmtime 36.0.18 (#14724)
Compare
WASI preview 0 implementation of poll_oneoff circumvents fuel consumption. GHSA-j366-h8gg-77pm
Released 2026-10-02.
WASI preview 0 implementation of poll_oneoff circumvents fuel consumption.
GHSA-j366-h8gg-77pm
Excessive allocated memory on the host when guests don't have stdio. GHSA-gqmc-89g8-p25r
fd_readdir copies uninitialized struct padding into guest memory.
GHSA-96f6-r43r-8c24
v36.0.17: Release Wasmtime 36.0.17 (#14472)
Compare
Fix fuel spend for dynamic record lifting. GHSA-jqpg-j7w6-42pr
Released 2026-09-24.
Fix fuel spend for dynamic record lifting. GHSA-jqpg-j7w6-42pr
Fix host memory exhaustion on outgoing HTTP body write. GHSA-c9gc-w9vx-w86p
wasmtime-wasi: Fix panic on out-of-range datetimes in WASI filesystem set-times, set-times-at. GHSA-j2g9-4prp-pf6h
v36.0.16: Release Wasmtime 36.0.16 (#14402)
Compare
Wasmtime's internal implementation of wasmtime-wasi no longer depends on cap-std crates for the underlying implementation. Instead the cap-std impleme
Released 2026-09-10
wasmtime-wasi no longer depends on
cap-std crates for the underlying implementation. Instead the cap-std
implementation was vendored into wasmtime-wasi. This is intended to have no
visible side effects or result in any behavior changes.
#14219v36.0.15: Release Wasmtime 36.0.15 (#14309)
Compare
Filesystem sandbox escape when paths or symlinks contain trailing slashes. GHSA-vqjp-4c8c-hfgg
Released 2026-08-20
v36.0.14: Release Wasmtime 36.0.14 (#14172)
Compare
Stores can mix up type indices between engines. GHSA-hgjw-h833-99q9
Released 2026-07-31.
v36.0.13: Release Wasmtime 36.0.13 (#14035)
Compare
WASI hard links and renames check wasmtime-wasi's FilePerms for destination GHSA-4ch3-9j33-3pmj
Released 2026-06-24.
Leak in WASIp1 fd_renumber implementation. GHSA-3p27-qvp9-27qf
WASI path_open(TRUNCATE) bypasses FilePerms::WRITE host restriction. GHSA-2r75-cxrj-cmph
Released 2026-05-21.
FilePerms::WRITE host restriction.
GHSA-2r75-cxrj-cmphCranelift's timing infrastructure is now more robust in the face of buggy system clocks. #12709 #13253
Panic when allocating a table exceeding the size of the host's address space. GHSA-p8xm-42r7-89xg
Released 2026-04-30.
Miscompiled guest heap access enables sandbox escape on aarch64 Cranelift. GHSA-jhxm-h53p-jm7w
Released 2026-04-09.
Miscompiled guest heap access enables sandbox escape on aarch64 Cranelift. GHSA-jhxm-h53p-jm7w
Wasmtime with Winch compiler backend may allow a sandbox-escaping memory access. GHSA-xx5w-cvp6-jv83
Out-of-bounds write or crash when transcoding component model strings. GHSA-394w-hwhg-8vgm
Host panic when Winch compiler executes table.fill.
GHSA-q49f-xg75-m9xw
Wasmtime segfault or unused out-of-sandbox load with f64x2.splat operator
on x86-64.
GHSA-qqfj-4vcm-26hv
Improperly masked return value from table.grow with Winch compiler backend.
GHSA-f984-pcp8-v2p7
Panic when transcoding misaligned utf-16 strings. GHSA-jxhv-7h78-9775
Panic when lifting flags component value.
GHSA-m758-wjhj-p3jq
Heap OOB read in component model UTF-16 to latin1+utf16 string transcoding. GHSA-hx6p-xpx3-jvvv
Data leakage between pooling allocator instances. GHSA-6wgr-89rj-399p
Host data leakage with 64-bit tables and Winch. GHSA-m9w2-8782-2946
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
Released 2026-02-24.
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-9p4wwasi:http/types.fields has been
resolved
GHSA-243v-98vx-264hFixed 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
Released 2026-01-26.
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.A possible stack overflow in the x64 backend with cmp emission has been fixed. #12333
Released 2026-01-14.
cmp emission has been
fixed.
#12333Prevent using shared memories with Memory. CVE-2025-64345
Wasmtime will no longer panic in the pooling allocator when in near-OOM conditions related to resetting the linear memory of a slot. #11510
Released 2025-08-26.
Accessors for internal WASI-related contexts are added to wasmtime_wasi::WasiCtx to account for refactorings that happened in this release. #11473
Released 2025-08-21.
wasmtime_wasi::WasiCtx to account for refactorings that happened in this
release.
#11473Cranelift's has initial support for inlining between functions. Wasmtime additionally now has support for inlining as well, for example between module
Released 2025-08-20.
Cranelift's has initial support for inlining between functions. Wasmtime additionally now has support for inlining as well, for example between modules in a component. #11210 #11239 #11228 #11269 #11283
The async proposal for the Component Model is now fully implemented in Wasmtime with a number of WASIp3 interfaces implemented. The implementation is still off-by-default and the implementation of WASIp3 is not fully complete, but is remains suitable for testing. #11127 #11136 #11137 #11238 #11221 #11250 #11257 #11291 #11325
Users who implemented WasiHttpView::is_forbidden_header from
wasmtime-wasi-http now need to include DEFAULT_FORBIDDEN_HEADERS, e.g.
DEFAULT_FORBIDDEN_HEADERS.contains(name) || name.as_str() == "custom-forbidden-header"
#11292
Cranelift's incremental cache has received some optimizations. #11186
Wasmtime's internal implementations of WebAssembly primitives has been refactored to be modeled with safer internal primitives. #11211 #11212 #11216 #11229 #11215 #11254 #11255 #11319 #11320
Detection of native hardware features has been refactored on s390x. #11220
Further progress has been made towards an implementation of the WebAssembly exceptions proposal, although it is not yet complete. #11230 #11321
Cranelift's assembler for x64 now supports EVEX encoding. #11153 #11270 #11303
The default implementation of send_request in the wasmtime-wasi-http crate
is now behind an on-by-default feature gate.
#11323
Configuration of the bindgen! macro has been redesigned to more consistently
configure per-function options such as whether or not it's async.
#11328
Initial support fo mutatis has been added to Wasmtime's fuzzers.
#11290
The debug-builtins crate feature of wasmtime no compiles on no_std
targets.
#11304
Deserializing external modules no long unnecessarily requires the allocation to be aligned. #11306
A CMake linker error and warning when using the C API on macOS has been fixed. #11293 #11315
The C API declaration of wasmtime_component_linker_instance_add_func has
been fixed.
#11327
The calculation of reachable DWARF has been fixed. #11338
Fix a panic in the host caused by preview1 guests using fd_renumber. CVE-2025-53901.
Released 2025-07-22.
A new InputFile type has been added for specifying stdin as a file in WASI.
#10968
Conditional branches to unconditional traps are now translated to conditional traps during legalization. #10988
The TE HTTP header can now be specified by guests.
#11002
Winch on AArch64 should now pass all WebAssembly MVP tests. Note that it is still not yet Tier 1 at this time, however. #10829 #11013 #11031 #11051
The x64 backend now has lowering rules for {add,sub,or,and} mem, imm
#11043
Initial support for WASIp2 in the C API has started to land. #11055 #11172
Initial support for GC support in the component model has started to land (note that it is not finished yet). #10967 #11020
The wasmtime-wasi-nn crate now has a feature to use a custom ONNX runtime.
#11060
Cranelift now optimizes division-by-constant operations to no longer use division. #11129
A native-tls backend has been added for the wasi-tls implementation.
#11064
Many more instructions for the x64 backend in Cranelift were migrated to the new assembler. #10927 #10928 #10918 #10946 #10954 #10958 #10971 #10942 #10975 #11017 #10898 #10836 ... (and more)
Wasmtime internally uses Pin for VM data structures to make the internal
implementations more sound to use. This has no effect on the public API of
Wasmtime.
#10934
#10937
#10943
#10959
#11042
Fused adapters between components now transfer the enum component model type
more efficiently.
#10939
Filenames of --emit-clif now match the symbol names found in *.cwasm
artifacts and include the function name as well.
#10947
#11040
Wasmtime-internal crates are now all named wasmtime-internal-* to even
further discourage their use.
#10963
Codegen of conditional traps with float compares has been improved. #10966
More patterns are now optimized in ISLE mid-end rules. #10978 #10979 #11173
Winch's support for constants/scratch registers has been improved internally. #10986 #10998
The C API artifacts on Windows are now produced with Clang instead of
cl.exe.
#10890
WebAssembly operand types are now taken into account during translation to optimize codegen better in the face of subtyping. #11030
The behavior of blocking-write-and-flush has been updated during flushing
when closed is found.
#11018
WASI WITs have been updated to 0.2.6. #11049
OpenVINO has been updated to v2025.1. #11054
The size of the wasmtime.addrmap section in *.cwasm artifacts has been
shrunk slightly.
#11126
Authorities in wasmtime-wasi-http can now contain the : character.
#11145
Wasmtime now requires Rust 1.86 to compile. #11142
Wasmtime's DRC collector has been optimized and has a new more efficient means of managing the set of over-approximated roots on the stack. #11144 #11148 #11167 #11168 #11169 #11175
The ComponentType trait in Wasmtime now requires the Send and Sync
bounds for all implementors.
#11160
The V128 type is now usable on platforms other than aarch64 and x86_64.
#11165
Wasmtime's policy on unsafe code and guidelines has been added.
#11177
The std crate will no longer implicitly be used on cfg(unix) and
cfg(windows) targets when the std Cargo feature is disabled. This means
that these platforms now require std to be enabled to use the
platform-specific implementation of linear memory, for example.
#11152
A panic when optimizing icmp with vectors has been fixed.
#10948
A panic when lowering scalar_to_vector with i16x8 types has been fixed.
#10949
The vector state register is now considered clobbered by calls on riscv64 to ensure it's updated across calls. #11048
An instance of gdb crashing on DWARF emitted by Wasmtime has been fixed.
#11077
Fix a panic in the host caused by preview1 guests using fd_renumber.
CVE-2025-53901.
Fix a panic in the preview1 adapter caused by guests using fd_renumber.
#11277
One column per month.