This would mean that for example bump to WASI SDK 22 in the VM images would automatically break runtime main. Is that what we want ?

cc @lewing

That's how the infrastructure team wants to maintain these images, yes. The point is getting OS etc. updates automatically.
If we know a new wasi sdk version breaks existing consumers then we need to create a new image.

I guess it'd makes sense to including the wasi sdk version number in the image name.

That's how the infrastructure team wants to maintain these images, yes. The point is getting OS etc. updates automatically. If we know a new wasi sdk version breaks existing consumers then we need to create a new image.

We don't know that, but WASI SDK 20 -> 21 required other changes to work. Like LLVM version bump.

I guess longer term we should move to using our own nuget packages for emsdk/wasi-sdk, then this wouldn't matter.

Merging since the floating tag refers to the same version so there's no point in wasting CI resources.