fix(deps): update rust dependencies to v44 (major)#14
Merged
Conversation
caecde7 to
d7d9d5f
Compare
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
41→4442→4442→4442→44Release Notes
bytecodealliance/wasmtime (wasi-preview1-component-adapter-provider)
v44.0.1Compare Source
44.0.1
Released 2026-04-30.
Fixed
GHSA-p8xm-42r7-89xg
v44.0.0Compare Source
44.0.0
Released 2026-04-20.
Added
The
wasmtimeCLI now supports a-gflag which runs a built-in wasm programto host a
gdbstub-compatible server (can be connected to with LLDB) to debugguest programs.
#12756
#12771
#12856
#12859
Wasmtime now has experimental support for the
map<K, V>type in thecomponent model.
#12216
Wasmtime's C API now supports wasm tag types.
#12763
#12803
Wasmtime's C API now supports exceptions.
#12861
Wasmtime's C API has more support for the GC proposal.
#12914
#12915
#12916
#12917
An initial implementation of the
wasi:tlsproposal for the 0.3.0-draftversion has been added.
#12834
Changed
The
demangleCargo feature of thewasmtimecrate is now compatible withno_stdtargets.#12740
The
wasmtime-wasi-tls-*crates are now merged into one crate with featureflags for each backend.
#12780
Wasmtime now requires Rust 1.92.0 or later to build.
#12828
The
cranelift-codegencrate now compiles forno_stdtargets.#12812
The
csdbinstruction, a defense-in-depth measure for spectre, is no longeremitted by default on aarch64 to match what peer runtimes are doing. In some
situations this is known to provide up to a 6x performance boost on macOS as
well.
#12932
Fixed
Wasmtime's native DWARF has been improved on aarch64 to support recovering
values more frequently.
#12779
A significant number of minor issues have been fixed throughout this release.
In addition to the security advisories found by LLMs there have also
been a large number of other issues identified as well. Many minor fixes are
present in this release for various situations for issues found in this
manner.
v43.0.2Compare Source
43.0.2
Released 2026-04-30.
Fixed
GHSA-p8xm-42r7-89xg
v43.0.1Compare Source
43.0.1
Released 2026-04-09.
Fixed
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.splatoperatoron x86-64.
GHSA-qqfj-4vcm-26hv
Improperly masked return value from
table.growwith Winch compiler backend.GHSA-f984-pcp8-v2p7
Panic when transcoding misaligned utf-16 strings.
GHSA-jxhv-7h78-9775
Panic when lifting
flagscomponent value.GHSA-m758-wjhj-p3jq
Heap OOB read in component model UTF-16 to latin1+utf16 string transcoding.
GHSA-hx6p-xpx3-jvvv
Use-after-free bug after cloning
wasmtime::Linker.GHSA-hfr4-7c6c-48w2
Data leakage between pooling allocator instances.
GHSA-6wgr-89rj-399p
Host data leakage with 64-bit tables and Winch.
GHSA-m9w2-8782-2946
v43.0.0Compare Source
43.0.0
Released 2026-03-20.
Added
Wasmtime now supports the WASIp3 snapshot
0.3.0-rc-2026-03-15.#12557
The number of frames captured in backtrace collection can now be configured.
#12542
Wasmtime now supports fine-grained operator cost configuration for when fuel
is enabled.
#12541
Configuring the
gc_supportoption is now possible through the C API.#12630
Configuring the
concurrency_supportoption is now possible through the CAPI.
#12703
Debugging-related APIs have been added to access all modules and instances on
a store.
#12637
All store entities now expose a "unique ID" for debugging purposes.
#12645
Cranelift's x64 backend now supports the
clsinstruction for all integertypes.
#12644
Changed
Internal refactoring and support necessary for handling OOM gracefully
throughout the runtime is proceeding apace. New APIs such as
FuncType::try_neware available in addition to many internal changes.#12530
#12537
(... and many more ...)
Wasmtime's representation of stack frames in the debugging API no longer
borrows the store itself and is instead represented as a handle.
#12566
Wasmtime now unconditionally sets
SO_REUSEADDRfor guest-bound sockets.#12597
Cranelift now supports more
VRegs which means effectively that largerfunctions will be compilable by default rather than returning a "function too
large" error.
#12611
WASIp3 implementations now limit returned memory by default for randomness and
HTTP headers.
#12745
#12761
Fixed
Running
wasmtime wizerover components with modules that contain an_initializefunction no longer removes the function to preserve the validityof the component.
#12540
Borrow state for host async tasks is now handled more correctly throughout
Wasmtime, especially in the face of cancellation.
#12550
Bindings generation now accounts for the fact that
futureandstreamarenot cloneable types.
#12155
The impementation of UDP in WASIp2 has had some wakeup-related bugs fixed.
#12629
Cancellation of host subtasks for component-model-async has been improved and
works more reliably.
#12640
Subtask management for component-model-async now no longer reparents which
fixes a number spec-related divergences.
#12570
Converting a
wasmtime::Errorintoanyhow::Errorand usingdowncasthasbeen fixed.
#12689
Async stream/future read/write cancellation has had some corner cases fixed.
#12704
Cranelift's timing infrastructure is now more robust in the face of buggy
system clocks.
#12709
The currently running guest task has been corrected in a number of cases
related to component-model-async and cooperative threading.
#12718
#12735
#12736
#12737
An issue of lost wakeups with the WASIp3 stdin implementation has been fixed.
#12745
v42.0.2Compare Source
42.0.2
Released 2026-04-09.
Fixed
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.splatoperatoron x86-64.
GHSA-qqfj-4vcm-26hv
Improperly masked return value from
table.growwith Winch compiler backend.GHSA-f984-pcp8-v2p7
Panic when transcoding misaligned utf-16 strings.
GHSA-jxhv-7h78-9775
Panic when lifting
flagscomponent 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
v42.0.1Compare Source
42.0.1
Released 2026-02-25.
Fixed
bindgen!issues withanyhow: true#12658
v42.0.0Compare Source
42.0.0
Released 2026-02-20.
Added
Cranelift now supports bitwise operations on floats on aarch64.
#12326
Cranelift now supports NaN canonicalization of f16 and f128.
#12337
Wasmtime has gained minimal support to implement fixed-length lists in the
component model being communicated between composed components.
#10619
Wasmtime's
ErrorandResulttypes are now built-in to thewasmtimecrateand are no longer defined by the
anyhowcrate. Wasmtime exports amostly-compatible
anyhow-like API atwasmtime::errorwhich is usedinstead. Wasmtime's own
Errorhandles OOM internally and is foundationalpart of Wasmtime's work-in-progress support to gracefully handle OOM.
#12309
Wasmtime now exports an extension trait to convert
anyhow::Result<T>intowasmtime::Result<T>.#12255
Wasmtime supports a new
bindgen!option to generate bindings specificallywith
anyhow::Resultinstead ofwasmtime::Result.#12331
The Nvidia-Cuda execution provider is now supported for the wasi-nn onnx
backend.
#12044
Non-exported and private entities can now be accessed through the debugger
API.
#12367
A new
Store::try_newAPI has been added which handles OOM.#12415
Initial configuration knobs for record-and-replay support have been added.
#12375
Cranelift's s390x backend now has support for instructions added in z17.
#12319
Wasmtime's implementation of fibers can now be compiled on riscv32imac
platforms.
#12506
Wasmtime's implementation of WASI now correctly limits resource consumption on
behalf of the guest, such as host-allocated memory, by default. This means
that some behaviors previously allowed by Wasmtime are now disallowed by
default if they rely on transferring a large amount of data from the guest to
the host. Additionally calls to
wasi:random/random.get-random-bytes, forexample, now have limits in place by default to avoid allocating too much
memory on the host. For more information on this see the related security
advisory with further details on knobs added and what behaviors are now
restricted by default.
GHSA-852m-cvvp-9p4w
Changed
Reentrance rules for WebAssembly components have changed in accordance with
upstream specification changes. Embeddings are not expected to be affected,
but please reach out if you find problems.
#12349
Wasmtime's
Config::async_supportoption is now removed and no longernecessary. Embeddings can likely just remove turning this on and everything
should keep working like normal.
#12371
Wasmtime now supports
Config::concurrency_supportas a knob to enable ordisable
*_concurrentAPIs at runtime when thecomponent-model-asynccratefeature is enabled.
#12416
The
post_return-style functions in Wasmtime's API are now noops and will beremoved in the future.
#12498
Translation of
global.getof a defined, immutable global is now turned intoa CLIF constant.
#12234
The
wasmtime-wasi-nncrate's dependency onorthas been updated.#12162
Error bounds requiring using
hyper::Errorinwasmtime-wasi-httphave beenrelaxed to taking
E: Into<ErrorCode>instead.#12227
The
cranelift-assembler-x64, andcranelift-islecrates now supportsno_std targets. The
cranelift-codegencrate now mostly supports no_std,but not entirely.
#12222
#12235
#12236
Android release binaries are now compiled with a larger page size configured.
#12246
Implicit binds are now allowed for WASIp3 sockets.
#12225
Wasmtime's implementation of component-model-async now correctly checks for
whether tasks are allowed to block in all guest-to-guest situations.
#12282
The
wasmtime-wasi-tlscrate now has an OpenSSL backend.#12228
Wasmtime's
OutOfMemoryerror now keeps track of the attempted allocationsize that failed.
#12351
Wasmtime's
*_uncheckedfunctions now work withMaybeUninit<ValRaw>insteadof
ValRawdirectly.#12366
Wasmtime now requires Rust 1.91.0 to compile.
#12392
Wasmtime's management of component-model-async tasks is now consistently done
in all boundaries between guest/host tasks.
#12379
Fixed
The
HeapType::matchesimplementation forNoExnhas been fixed.#12350
Enum discriminant validation for composed components has been fixed.
#12356
Shifts in some situations on aarch64 with Winch have been fixed.
#12501
Debug value locations around cold blocks have been improved.
#12484
Panics when adding too many headers to a
wasi:http/types.fieldshas beenresolved
GHSA-243v-98vx-264h
v41.0.4Compare Source
41.0.4
Released 2026-02-24.
Changed
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 placeto 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.fieldshas beenresolved
GHSA-243v-98vx-264h
Panic when dropping a
[Typed]Func::call_asyncfuture.GHSA-xjhv-v822-pf94
v41.0.3Compare Source
41.0.3
Released 2026-02-04.
Fixed
due to mismatched types.
#12504
v41.0.2Compare Source
41.0.2
Released 2026-02-03.
Fixed
wasmtime-internal-jit-icache-coherencecrate.#12446
Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.