Stream: wasmtime

Topic: wasm-tools v1.224.1/1.225.0 releases


view this post on Zulip Victor Adossi (Mar 13 2025 at 05:06):

Hey all, just discovered a couple things:

Currently I'm recommending installing from GH releases (the binary there) for 1.224.1 and 1.225.0 via cargo, but wanted to surface here

view this post on Zulip Alex Crichton (Mar 13 2025 at 14:31):

For 1.225.0 I think it's here -- https://github.com/bytecodealliance/wasm-tools/releases/tag/v1.225.0 -- although that's on the second page of tags due to a bunch of point releases being done after that

What's Changed Fix std feature in wasm-encoder by @ark0f in #1961 Update spec test suite submodule by @alexcrichton in #1984 Fix cargo doc warnings by @samestep in #1986 Catch cargo doc warnings i...

view this post on Zulip Victor Adossi (Mar 13 2025 at 14:35):

Ah thank you -- :man_facepalming: just didn't think it could have shifted that far down

view this post on Zulip Alex Crichton (Mar 13 2025 at 14:38):

For 1.224.1 I'm as perplexed as you

view this post on Zulip Alex Crichton (Mar 13 2025 at 14:39):

I can reproduce it and I'm trying to figure out why our CI checks didn't discover that

view this post on Zulip Victor Adossi (Mar 13 2025 at 14:39):

Should definitely be impossible :tm:

view this post on Zulip Victor Adossi (Mar 13 2025 at 14:39):

especially under --locked

view this post on Zulip Alex Crichton (Mar 13 2025 at 14:43):

ok it looks like the Cargo.lock with wasm-tools 1.224.1 doesn't match what's in the source tree and that's what's going on

view this post on Zulip Alex Crichton (Mar 13 2025 at 14:44):

not sure why that's happening though

view this post on Zulip Alex Crichton (Mar 13 2025 at 14:49):

https://github.com/bytecodealliance/wasm-tools/pull/2098 is one issue at least

This fixes an unfortunate series of events which renders most historical builds of wasm-tools un-buildable from crates.io without --locked. The basic problem here is of this shape: The wasm-tools ...

Last updated: Apr 10 2025 at 05:03 UTC