Unverified50% confidenceFactExact time
In the semantic versioning (SemVer) system, suffixes such as -pre, -alpha, -beta, and -rc are collectively called pre-release identifiers, and their sorting priority is lower than the corresponding official version.
1
Sources
50%
Confidence
Long-term
Relevance
10/14/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedPre-release tags in the Semantic Versioning specification follow priority ordering; in Cargo, "^1.19.0" will not match "1.19.1-pre", as pre-release versions are not included in normal version range matching by default.68% similarUnverifiedIn the SemVer specification, a pre-release identifier has lower precedence than the corresponding official version, for example 1.24.2-pre < 1.24.2.68% similarUnverifiedA formal semantic version number (such as v1.0+) indicates the author considers the project stable, while remaining at the rc, alpha, or beta stage indicates it is not yet mature.68% similarUnverifiedactions/python-versions handles stable versions and pre-release versions (alpha, beta, rc) separately, and only official stable versions are included in the default available list.65% similarUnverifiedPrompts should be stored in a version-controlled repository and tagged with semantic version numbers; the major version number corresponds to breaking changes in the output contract, the minor version number to behaviour-enhancing but structurally compatible adjustments, and the patch number to typo and explanatory text fixes.64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1029130API
curl https://kongchang.com/api/v1/knowledge/claims/1029130MCP
get_claim(id=1029130)