Unpin wasi docker image in pipeline-with-resources.yml

[akoeplinger]

No description provided.

[pavelsavara]

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

[akoeplinger]

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.

[pavelsavara]

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.

[akoeplinger]

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

[akoeplinger]

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