Repository navigation
Release tag/name version and released file versions differ by a .0 #360
Description
Activity
For wasi-sdk-21, I thought about this a bit: on the one hand, whatever scripts are out there have probably adapted to this inconsistency so "fixing" it might actually break other people's workflows. Also, having the minor version present is probably useful in case someone needs to patch a release. On the other hand, perhaps we could tag releases twice:
wasi-sdk-Nandwasi-sdk-N.M. Then users of wasi-sdk could choose whichever tag best suits their workflow. That could get confusing, though, so ideally we could improve the release workflow in CI to just "do the right thing" automatically.whatever scripts are out there have probably adapted to this inconsistency so "fixing" it might actually break other people's workflows.
True (me included).
Also, having the minor version present is probably useful in case someone needs to patch a release.
But if that was ever not
.0then that would also break people.No good options, unfortunately, short of getting into package managers so it's their problem. 😉
The released files for the WASI SDK all have a
.0at the end of their version, while the release names/tags don't. For example, https://github.com/WebAssembly/wasi-sdk/releases/tag/wasi-sdk-20 has https://github.com/WebAssembly/wasi-sdk/releases/download/wasi-sdk-20/wasi-sdk-20.0-linux.tar.gz ; notice the20in the tag name but20.0in the file name.This makes it a little tricky to download files as both names are used in the URL. For example, in a Docker file I have (notice the hard-coded
.0in that URL):ENV WASI_SDK_VERSION=20 curl --location https://github.com/WebAssembly/wasi-sdk/releases/download/wasi-sdk-${WASI_SDK_VERSION}/wasi-sdk-${WASI_SDK_VERSION}.0-linux.tar.gzMaking sure to not leave off that
.0is easy to forget. Same goes for where the tarball expands to (luckily in this case I can usetar --strip-components 1 --directory ${WASI_SDK_PATH}to avoid this, but on my development machine I can't).Any chance future git tags/GitHub releases can include the full version?