chore(deps): update rust crate wasmtime to v40.0.4#123
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
chore(deps): update rust crate wasmtime to v40.0.4#123renovate[bot] wants to merge 1 commit intomainfrom
renovate[bot] wants to merge 1 commit intomainfrom
Conversation
8a06889 to
dea56e0
Compare
dea56e0 to
fd16d79
Compare
fd16d79 to
2f56190
Compare
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:
40.0.0→40.0.4Release Notes
bytecodealliance/wasmtime (wasmtime)
v40.0.4Compare Source
40.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
v40.0.3Compare Source
40.0.3
Released 2026-01-26.
Fixed
f64.copysignon x86-64 whereby when combinedwith an
f64.load, the resulting machine code could read 16 bytes ratherthan 8 bytes. This could result in a segfault when Wasmtime is configured
without signals-based traps.
v40.0.2Compare Source
40.0.2
Released 2026-01-14.
Fixed
A possible stack overflow in the x64 backend with
cmpemission has beenfixed.
#12333
Some ISLE optimization rules which created erroneous IR for vector inputs have
been fixed.
#12179
#12335
The x64 lowering of
shldhas been fixed for some edge caxes.#12321
v40.0.1Compare Source
40.0.1
Released 2026-01-07.
Changed
Wasmtime is switching to crates.io-based trusted publishing for this release
and is testing that everything works.
#12257
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 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 this update again.
This PR was generated by Mend Renovate. View the repository job log.