I'm planning on cutting a new release; any reason that should wait? Any super critical PR that needs to be merged first?
Someone want to rubber stamp this? https://github.com/bytecodealliance/wasmtime/pull/2557
Will do
merged; tag pushed to github; publishing to crates.io now
@Alex Crichton can you make me and/or the wasmtime publishers team a crates.io owner for:
peepmatic-traits
cranelift-interpreter
wasmtime-cranelift
wasmtime-lightbeam
wasmtime-cache
Does someone want to tweet about the release?
I can tweet it out once I've published to crates.io
@fitzgen (he/him) ok sent invites for all those, sorry about that!
@Alex Crichton oh also cranelift-serde
please
@fitzgen (he/him) done!
thanks!
ugh now cloudfront thinks I am making too many requests to crates.io
alright, finally got all the crates on crates.io so the release is complete!
announcement tweet over here: https://twitter.com/fitzgen/status/1347603425471590405
:loudspeaker: Announcing Wasmtime v0.22.0! :loudspeaker: Now with support for :link: the module-linking proposal and 🧠 wasi-nn! Full CHANGELOG: https://github.com/bytecodealliance/wasmtime/blob/main/RELEASES.md#0220 Assets: https://github.com/bytecodealliance/wasmtime/releases/tag/v0.22.0 Learn more at https://docs.wasmtime.dev/
- fitzgen (@fitzgen)if possible, could you also push cranelift-jit
to crates? since the rename from cranelift-simplejit
EDIT: whoops just noticed thats done already!
Last updated: Dec 23 2024 at 14:03 UTC