From fd042f9b1a1030f8200b4347d5f2a3ecee2fcbf2 Mon Sep 17 00:00:00 2001 From: Thomas Heartman Date: Wed, 9 Mar 2022 10:51:24 +0100 Subject: [PATCH] docs: update semver format after discussion and alignment --- website/docs/advanced/strategy-constraints.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/website/docs/advanced/strategy-constraints.md b/website/docs/advanced/strategy-constraints.md index 0311783f60..500780a339 100644 --- a/website/docs/advanced/strategy-constraints.md +++ b/website/docs/advanced/strategy-constraints.md @@ -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 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` -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). You can read more about SemVer in [the full SemVer specification](https://semver.org/).