1
0
mirror of https://github.com/Unleash/unleash.git synced 2025-02-04 00:18:01 +01:00

docs: update semver format after discussion and alignment

This commit is contained in:
Thomas Heartman 2022-03-09 10:51:24 +01:00
parent db9a0e2c54
commit fd042f9b1a

View File

@ -135,12 +135,9 @@ String operators differ from the other categories in two different ways:
The SemVer operators are used to compare version numbers such as application versions, dependency versions, etc. The SemVer operators are used to compare version numbers such as application versions, dependency versions, etc.
The SemVer input must follow a few rules: The SemVer input must follow a few rules:
- The value you enter must at least consist of three version numbers separated by full stops. Example: `1.2.3` - The value you enter **must** start with and contain at least major, minor, and patch versions: Example: `1.2.3`
- Optionally, you can also add pre-release version information by adding a hyphen and series of dot separated identifiers after the patch version. Example: `1.2.3-rc.2` - Optionally, you can also add pre-release version information by adding a hyphen and series of dot separated identifiers after the patch version. Example: `1.2.3-rc.2`
You can enter SemVer values with or without a leading "v": `v1.2.3` and `1.2.3` are both valid.
Importantly, they are also considered equal.
Versions with pre-release indicators (e.g. `4.8.0-rc.2`) are considered *less than* versions without (e.g. `4.8.0`) in accordance with [the SemVer specification, item 11](https://semver.org/#spec-item-11). Versions with pre-release indicators (e.g. `4.8.0-rc.2`) are considered *less than* versions without (e.g. `4.8.0`) in accordance with [the SemVer specification, item 11](https://semver.org/#spec-item-11).
You can read more about SemVer in [the full SemVer specification](https://semver.org/). You can read more about SemVer in [the full SemVer specification](https://semver.org/).