juntyr opened issue #11424:
The automatic publish CI failed for v35 and it looks like some crates where then published manually. Unfortunately, the wasi-preview1-component-adapter-provider crate seems to have been missed.
@alexcrichton Would you be able to publish v35 for wasi-preview1-component-adapter-provider manually?
alexcrichton commented on issue #11424:
We had an unfortunate series of events which led to v35 being pretty difficult to publish and alas I forgot to go back and take care of this crate. I'm hesitant to manually do this since this crate requires artifacts and arranging files in the right place. Would you be ok to use the v36 version that'll get published in a week?
pchickey commented on issue #11424:
The only recent change to the adapter has been https://github.com/bytecodealliance/wasmtime/pull/11277 and its backports - aside from the version number, 34.0.2 and 35.0.0 should be identical, and will be to 36.0.0 as well.
pchickey edited a comment on issue #11424:
The only recent change to the adapter has been https://github.com/bytecodealliance/wasmtime/pull/11277 and its backports - aside from the version number, 34.0.2 and 35.0.0 should be identical, and will be to 36.0.0 as well.
There may end up being other incidental changes, like the version of Rust used to build it and version bumps of dependencies like wit-bindgen that shouldn't make any functional difference.
juntyr closed issue #11424:
The automatic publish CI failed for v35 and it looks like some crates where then published manually. Unfortunately, the wasi-preview1-component-adapter-provider crate seems to have been missed.
@alexcrichton Would you be able to publish v35 for wasi-preview1-component-adapter-provider manually?
juntyr commented on issue #11424:
Would you be ok to use the v36 version that'll get published in a week?
Yes, that works as well! I've been looking forward to using wasi 0.2.6, the update for which was (as best as I know) included in v35.
Last updated: Dec 06 2025 at 07:03 UTC