Tag and publish releases

[atifsyedali]

Please create releases and tag the repository with each version. The recent change from wasi:keyvalue@0.2.0-draft to wasi:keyvalue@0.2.0-draft2 means that all wit-deps update effectively pulls in the https://github.com/WebAssembly/wasi-keyvalue/archive/main.tar.gz file with 0.2.0-draft2, but because some open-source implementations are still on 0.2.0-draft, this mismatch breaks existing solutions that are pulling in both the latest keyvalue WIT and the open source implementation on older version of the WIT.

[Mossaka]

yeah we need to do a better job at tagging each version. I will do that

[Mossaka]

Just tagged the v0.2.0-draft https://github.com/WebAssembly/wasi-keyvalue/releases/tag/v0.2.0-draft

[pchickey]

Can you post v0.2.0-draft2 as well with the current contents of main? I'm working on an implementation and would like to manage the wit with wkg. Right now the ghcr.io registry only has -draft.

[Mossaka]

We are holding on publishing v0.2.0-draft2 because I believe @ricochet and @thomastaylor312 are going to push a change to address #47

[thomastaylor312]

Yeah we fell behind on this (obviously). I also have some remaining work to come bring in an automatic publishing pipeline here, but maybe it would just be easier especially now that we're working on https://github.com/bytecodealliance/wkg-github-action

[mikkelhegn]

Is there a 0.1.0 version of this spec, which was ever released? It's unclear based on history and tags/releases?

[pchickey]

@mikkelhegn there is no version 0.1.0 of this spec. By convention, the first release version of this spec would be 0.2.x, to match with the rest of the WASI 0.2 specs, which are on a release train. Before release, which requires a WASI subgroup vote, proposal champions can tag versions 0.2.0-draftN whenever they feel its appropriate.

[mikkelhegn]

Thanks for the explanation @pchickey.