Note, that the interface version in the WIT is purposefully not changed - doing so (e.g. using 0.2.0-draft.1) means that hosts that would want to support both versions would now need to duplicate all binding implementations and deal with duplicate I/O package dependencies.
There's no reason for this complexity, however, because the host may choose any version of I/O package for implementation, e.g. component interface version depending on wasi:io/streams@0.2.2 can successfully import host interface version depending on wasi:io/streams@0.2.0 (see an example of this working in https://github.com/wasmCloud/wasmCloud/pull/3312 if interested)
Note, that the interface version in the WIT is purposefully not changed - doing so (e.g. using
0.2.0-draft.1) means that hosts that would want to support both versions would now need to duplicate all binding implementations and deal with duplicate I/O package dependencies.There's no reason for this complexity, however, because the host may choose any version of I/O package for implementation, e.g. component interface version depending on
wasi:io/streams@0.2.2can successfully import host interface version depending onwasi:io/streams@0.2.0(see an example of this working in https://github.com/wasmCloud/wasmCloud/pull/3312 if interested)