We detect a couple of supported RCs of wasi:http, plus releases 0.2.0 and 0.2.1. However, the wasi crate (https://docs.rs/wasi/latest/wasi/) has already moved on to 0.2.2, and will presumably move on to 0.2.3 etc. in other minor versions. This means users of the wasi crate in Spin apps have to pin to an exact patch version instead of the 0.13 minor version (see https://github.com/fermyon/leptos-spin/pull/48#discussion_r1847541217).
What would be the practicalities of enabling all 0.2 versions of wasi:http, present and future?
We detect a couple of supported RCs of
wasi:http
, plus releases0.2.0
and0.2.1
. However, thewasi
crate (https://docs.rs/wasi/latest/wasi/) has already moved on to 0.2.2, and will presumably move on to 0.2.3 etc. in other minor versions. This means users of thewasi
crate in Spin apps have to pin to an exact patch version instead of the 0.13 minor version (see https://github.com/fermyon/leptos-spin/pull/48#discussion_r1847541217).What would be the practicalities of enabling all 0.2 versions of
wasi:http
, present and future?cc @alexcrichton