Stream: wasmtime

Topic: How does wasmtime handle patch versions?


view this post on Zulip Bailey Hayes (Feb 05 2025 at 17:30):

Hello! I am looking for how wasmtime handles linking versions and documentation for how other runtimes are expected to handle non-breaking patch updates.

I believe the expectation is that runtimes that support older versions of WASI, e.g. 0.2.2, should successfully link to a component that has a newer patch version (0.2.3) if the new features are not used. Is that correct?

view this post on Zulip Pat Hickey (Feb 05 2025 at 17:37):

I don't know if there are docs, but heres the implementation https://github.com/bytecodealliance/wasmtime/blob/main/crates/environ/src/component/names.rs

A lightweight WebAssembly runtime that is fast, secure, and standards-compliant - bytecodealliance/wasmtime

view this post on Zulip Alex Crichton (Feb 05 2025 at 21:23):

You're correct bailey yeah. AFAIK we haven't documented this too well at this time. The theory though is wasmtime embedders update at their own cadence and they will naturally support both older and newer components unless bleeding edge features are used

view this post on Zulip Alex Crichton (Feb 05 2025 at 21:24):

That is, unless the guest is using bleeding edge features which requires updating wasmtime to get support

view this post on Zulip Pat Hickey (Feb 05 2025 at 22:02):

right. brand new feature in a patch version means the name wont be available in the prior version, so it wont resolve because the name doesnt exist.


Last updated: Feb 27 2025 at 23:03 UTC