Releases · bytecodealliance/wasmtime

26 Oct 15:53

github-actions

v14.0.2

2ade3ad

v14.0.2: Release Wasmtime 14.0.2 (#7367)

14.0.2

Released 2023-10-26

Fixed

Make the wasmtime::unix module accessible on macOS again.
#7360
Inter-crate dependencies between cranelift-* crates now disable the
default feature meaning that it's possible for embedders to depend on
cranelift-codegen as well without the default feature.
#7369

Assets 22

26 Oct 14:53

github-actions

v13.0.1

fddcc98

v13.0.1: Release Wasmtime 13.0.1 (#7375)

13.0.1

Released 2023-10-26

Fixed

Make the wasmtime::unix module accessible on macOS again.
#7360

Assets 22

23 Oct 18:38

github-actions

v14.0.1

402d3da

v14.0.1: Release Wasmtime 14.0.1 (#7334)

14.0.1

Released 2023-10-23

Fixed

Cranelift: preserve uext and sext flags for parameters on x86_64 and apple
aarch64. Note that this does not affect Wasmtime and is only intended for
Cranelift embedders such as rustc_codegen_cranelift.
#7333

Assets 22

20 Oct 16:31

github-actions

v14.0.0

2da78ca

v14.0.0: Release Wasmtime 14.0.0 (#7308)

14.0.0

Released 2023-10-20

One of the larger changes in this release is a redesign of Wasmtime's CLI
arguments and where arguments are passed. This means that previous invocations
of the wasmtime CLI executable will need to be updated. No functionality was
removed but most of it is behind new flags. One major change is that Wasmtime
CLI flags are now grouped behind short options like -O. For example

wasmtime run --opt-level 2 foo.wasm

is now:

wasmtime run -O opt-level=2 foo.wasm

Additionally options prefixed with --enable-* or --disable-* now
consistently are considered boolean setters. For example:

wasmtime run --disable-cache foo.wasm

is now:

wasmtime run -C cache=n foo.wasm

Options can be explored with wasmtime -C help for example, and wasmtime -h
will show all option groups that can be expanded.

Another major change in the CLI is that any CLI argument which positionally
comes after the wasm file specified will be passed as an argument to the guest
module. For example this invocations

wasmtime run foo.wasm --epoch-interruption

was previously accepted as enabling epoch interruption for the foo.wasm file.
This is now interpreted as if it were ./foo.wasm --epoch-interruption,
however, passing the flag to the wasm file itself. Flags to Wasmtime must now
come after Wasmtime's subcommand (in this case run) and before the wasm file
that's being run, for example:

wasmtime run -W epoch-interruption foo.wasm

More information about this change can be found on
#6925 and
#6946.

Added

Added the wasmtime::FrameInfo::module method, which returns the
wasmtime::Module associated with the stack frame.
The wasmtime::component::Linker type now implements Clone.
#7032
Wasmtime's TypedFunc API now supports the v128 WebAssembly type on x86_64
and aarch64.
#7010
Support for resources exported from a WebAssembly guest has been added to the
component bindgen! macro.
#7050
The C API now supports learning about a module's image_range.
#7064
Passing values between components is now possible with a more complete
implementation of type-checking of values.
#7065
Types representing resources can now be customized with bindgen!.
#7069
Wasm-defined globals and memories are now included in core dumps, and the
wasmtime::WasmCoreDump type is now serializable.
#6935
#7078
Initial experimental support for Intel MPK has been added to support running
more instances concurrently.
#7072
The implementation of wasi:http now supports inbound requests in addition to
outbound requests. A new wasmtime serve command is an example way of
handling http requests with wasm files.
#7091
The C API now supports Wasmtime's "host memory creation" API to customize the
allocation of linear memories.
#7115
The C API now supports asynchronous invocation of WebAssembly programs.
#7106
The C API now supports Wasmtime's InstancePre<T> type.
#7140
The wasi:sockets/ip-name-lookup interface is now implemented by Wasmtime.
#7109

Changed

Wasmtime's CLI has been significantly overhauled. See the note above.
#6925
#6946
The wasmtime::FrameInfo::module_name has been removed, however you can now
get identical results by chaining wasmtime::FrameInfo::module and
wasmtime::Module::name: my_frame.module().name().
WASI interfaces have seen significant work since the previous release. Streams
for example have a new backpressure and flushing design. Additionally WIT
resources are now used ubiquitously throughout the specification and
implementation.
#6877
#7029
#7090
The implementation of wasi:http now uses {input,output}-stream from the
wasi:io/streams interface.
#7056
Lifting and lowering of the list<u8> component values has been significantly
optimized.
#6971
The wasmtime-c-api crate is now additionally built as an rlib as well as the
previous cdylib/staticlib combo.
#6765

Fixed

Support referencing stack slots in the DWARF debug info.
#6960
Printing unicode to stdio on Windows has been fixed.
#6825
Building for x86_64-linux-android has been fixed.
#7055
Fixed stdout/stderr becoming nonblocking by accident with WASI preview2 on
macOS.
#7058
Fixed some character boundary-related panics in the preview2 implementation of
preview1.
#7011
Fixed an issue of guests sleeping for an incorrect amount of time with
preview2.
#6993
Cranelift will now return an error when running out of temporaries in a very
large function instead of panicking.
#7114

Assets 22

20 Sep 15:27

github-actions

v13.0.0

aec4b25

v13.0.0: Release Wasmtime 13.0.0 (#7067)

13.0.0

Released 2023-09-20

Added

Configuration of mach ports vs signals on macOS is now done through a Config
instead of at compile time.
#6807
Engine::detect_precompiled{,_file} can be used to to determine whether some
bytes or a file look like a precompiled module or a component.
#6832
#6937
A new feature "wmemcheck" has been added to enable Valgrind-like detection of
use-after-free within a WebAssembly guest module.
#6820
#6856
The wasmtime CLI now supports executing components.
#6836
Support for WASI preview2's TCP sockets interface has been added.
#6837
Wasmtime's implementation of the wasi-nn proposal now supports named models.
#6854
The C API now supports configuring native_unwind_info,
dynamic_memory_reserved_for_growth, target, and Cranelift settings.
#6896
#6934
The wasmtime crate now has initial support for component model bindings
generation for the WIT resource type.
#6886
Cranelift's RISC-V backend now has a complete implementation of the
WebAssembly SIMD proposal. Many thanks to Afonso Bordado for all their
contributions!
#6920
#6924
The bindgen! macro in the wasmtime crate now supports conditional
configuration for which imports should be async and which should be
synchronous.
#6942

Changed

The pooling allocator was significantly refactored and the
PoolingAllocationConfig has some minor breaking API changes that reflect
those changes.

Previously, the pooling allocator had count slots, and each slot had N
memories and M tables. Every allocated instance would reserve those N
memories and M tables regardless whether it actually needed them all or
not. This could lead to some waste and over-allocation when a module used less
memories and tables than the pooling allocator's configured maximums.

After the refactors in this release, the pooling allocator doesn't have
one-size-fits-all slots anymore. Instead, memories and tables are in separate
pools that can be allocated from independently, and we allocate exactly as
many memories and tables as are necessary for the instance being allocated.

To preserve your old configuration with the new methods you can do the following:
```
let mut config = PoolingAllocationConfig::default();

// If you used to have this old, no-longer-compiling configuration:
config.count(count);
config.instance_memories(n);
config.instance_tables(m);

// You can use these equivalent settings for the new config methods:
config.total_core_instances(count);
config.total_stacks(count); // If using the `async` feature.
config.total_memories(count * n);
config.max_memories_per_module(n);
config.total_tables(count * m);
config.max_tables_per_module(m);
```
There are additionally a variety of methods to limit the maximum amount of
resources a single core Wasm or component instance can take from the pool:
- PoolingAllocationConfig::max_memories_per_module
- PoolingAllocationConfig::max_tables_per_module
- PoolingAllocationConfig::max_memories_per_component
- PoolingAllocationConfig::max_tables_per_component
- PoolingAllocationConfig::max_core_instances_per_component
These methods do not affect the size of the pre-allocated pool.
#6835
Builder methods for WASI contexts now use &mut self instead of self.
#6770
Native unwinding information is now properly disabled when it is configured to
be turned off.
#6547
Wasmtime's minimum supported Rust version (MSRV) is now 1.70.0. Wasmtime's
MSRV policy of supporting the last three releases of Rust (N-2) is now
additionally documented. More discussion can additionally be found on the PR
itself.
#6900
Wasmtime's support for DWARF debugging information has seen some fixes for
previously reported crashes.
#6931

Removed

Wasmtime's experimental implementation of wasi-crypto has been removed. More
discussion of this change can be found on
#6732
and
#6816
Support for union types in the component model has been removed.
#6913

Assets 22

14 Sep 22:24

github-actions

v12.0.2

79a5d2a

v12.0.2: [12.0.0] Fix test expectations (#7038)

* Fix test expectations

[automatically-tag-and-release-this-commit]

* CI: upgrade to qemu 8.0.4. (#6849)

* CI: upgrade to qemu 8.0.4.

This should resolve a bug in qemu triggered by changes in #6820
(see
[here](https://github.com/bytecodealliance/wasmtime/pull/6820#issuecomment-1678908361)).

* ci: Update QEMU patch for 8.0.2

---------

Co-authored-by: Afonso Bordado <[email protected]>

---------

Co-authored-by: Chris Fallin <[email protected]>
Co-authored-by: Afonso Bordado <[email protected]>

Assets 22

14 Sep 22:21

github-actions

v11.0.2

2d29546

v11.0.2: [11.0.0] Fix test expectations (#7039)

* Fix test expectations

[automatically-tag-and-release-this-commit]

* CI: upgrade to qemu 8.0.4. (#6849)

* CI: upgrade to qemu 8.0.4.

This should resolve a bug in qemu triggered by changes in #6820
(see
[here](https://github.com/bytecodealliance/wasmtime/pull/6820#issuecomment-1678908361)).

* ci: Update QEMU patch for 8.0.2

---------

Co-authored-by: Afonso Bordado <[email protected]>

---------

Co-authored-by: Chris Fallin <[email protected]>
Co-authored-by: Afonso Bordado <[email protected]>

Assets 22

14 Sep 22:00

alexcrichton

v10.0.2

38524ca

v10.0.2: Release Wasmtime 10.0.2 (#6991)

Fix test expectations (#7040)

[automatically-tag-and-release-this-commit]

Assets 22

24 Aug 18:48

github-actions

v12.0.1

6116aae

v12.0.1: Release Wasmtime 12.0.1 (#6901)

* Release Wasmtime 12.0.1

[automatically-tag-and-release-this-commit]

* Update cargo-vet metadata

---------

Co-authored-by: Wasmtime Publish <[email protected]>
Co-authored-by: Alex Crichton <[email protected]>

Assets 22

21 Aug 21:34

github-actions

v12.0.0

54cbe5f

v12.0.0: Release Wasmtime 12.0.0 (#6864)

* Release Wasmtime 12.0.0

[automatically-tag-and-release-this-commit]

* Update release date to today

* Update release notes for 12.0.0

---------

Co-authored-by: Wasmtime Publish <[email protected]>
Co-authored-by: Alex Crichton <[email protected]>

Assets 22

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

14.0.2

Fixed

13.0.1

Fixed

14.0.1

Fixed

14.0.0

Added

Changed

Fixed

13.0.0

Added

Changed

Removed

Releases: bytecodealliance/wasmtime

v14.0.2: Release Wasmtime 14.0.2 (#7367)

14.0.2

Fixed

v13.0.1: Release Wasmtime 13.0.1 (#7375)

13.0.1

Fixed

v14.0.1: Release Wasmtime 14.0.1 (#7334)

14.0.1

Fixed

v14.0.0: Release Wasmtime 14.0.0 (#7308)

14.0.0

Added

Changed

Fixed

v13.0.0: Release Wasmtime 13.0.0 (#7067)

13.0.0

Added

Changed

Removed

v12.0.2: [12.0.0] Fix test expectations (#7038)

v11.0.2: [11.0.0] Fix test expectations (#7039)

v10.0.2: Release Wasmtime 10.0.2 (#6991)

v12.0.1: Release Wasmtime 12.0.1 (#6901)

v12.0.0: Release Wasmtime 12.0.0 (#6864)