Upstream versioning normalisation to comply with SemVer

[daichifukui]

Description

The current versioning scheme in wasix-libc could be improved for better compatibility with downstream packaging tools (e.g., Debian). Some releases include a trailing -0 (e.g., 1.2.3-0), often added during packaging to indicate a zero revision. While harmless upstream, it can cause confusion or version-sorting issues in downstream systems.

Similarly, hyphens in version numbers (e.g., 2025-09-02.1) can interfere with packaging tools that interpret the hyphen as a separator between the upstream version and revision. Using dots instead (e.g., 2025.09.02.1) avoids this problem and improves consistency.

The following resources provide relevant guidance:

• Debian Upstream Guide
• Semantic Versioning

Suggested action

• Consider adopting strict SemVer (e.g., 1.2.3 instead of 1-2-3).
• Prefer dots (.) over hyphens (-) in date-based or incremental versions.
• Update release automation or tagging scripts as needed.

Thanks for your attention to this!

[theduke]

Semver doesn't really make sense in this context, because they numbers would be meaningless and hold to the meaning of semver (major, minor, patch).

Thoughts, @Arshia001 ?

[onlyjob]

At least following Semver semantic would help downstream maintainers in Debian to work with normalised version notation. Creative versioning of wasix-libc requires correction downstream so that packaging tools could compare versions, etc. IMHO trailing -0 is already meaningless, and it would be helpful if it could be just dropped, because downstream package revision is typically separated from upstream version number by -. Thanks.