Release tag/name version and released file versions differ by a `.0`

The released files for the WASI SDK all have a .0 at 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 the 20 in the tag name but 20.0 in 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 .0 in 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.gz

Making sure to not leave off that .0 is easy to forget. Same goes for where the tarball expands to (luckily in this case I can use tar --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?

Use the Dockerfile example and the wasi-sdk-20 GitHub release as reproduction points. Trace the release packaging and naming entry points, then verify that the full version is used consistently in the tag, release asset, and extracted directory without requiring a hard-coded .0.