Change versioning scheme

We have to move away from using a semantic version with build information
(e.g. `v0.1.0+build12`) because this is not supported by OCI tag rules.

Because of that, we have to use the pre-release section
(e.g.`v0.1.0-rc1`).

Signed-off-by: Flavio Castelli <[email protected]>

Author: flavio

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "deprecated-api-versions"
-version = "0.1.0+k8sv1.26.0"
+version = "0.1.0-k8sv1.26.0"
 authors = ["Flavio Castelli <[email protected]>"]
 edition = "2018"
 

Cargo.toml

@@ -57,11 +57,11 @@ added this policy will be updated.
 The versioning scheme of this policy follows this pattern:
 
 ```
-<policy version>+k8sv<most recent version of kubernes known by the embedded deprecation rules>
+<policy version>-k8sv<most recent version of kubernes known by the embedded deprecation rules>
 ```
 
-For example, the release `0.1.0+k8sv1.26.0` of this policy knows about all the deprecation rules
+For example, the release `0.1.0-k8sv1.26.0` of this policy knows about all the deprecation rules
 formulated up to Kubernetes release 1.26.0.
 
 The announcement of new deprecation rules for Kubernetes 1.27.0 would trigger
-then a release of this policy with the following version: `v0.1.1+k8sv1.27.0`.
+then a release of this policy with the following version: `v0.1.1-k8sv1.27.0`.

README.md

@@ -1,5 +1,5 @@
 ---
-version: "0.1.0+k8sv1.26.0"
+version: "0.1.0-k8sv1.26.0"
 name: deprecated-api-versions
 displayName: Deprecated API Versions
 createdAt: '2022-11-03T16:39:10+02:00'

artifacthub-pkg.yml

@@ -48,10 +48,10 @@ pub fn main() {
     let current_policy_version = find_policy_version(&cli.manifest_path);
 
     let build_version =
-        semver::BuildMetadata::new(format!("k8sv{}", most_recent_k8s_version).as_str())
+        semver::Prerelease::new(format!("k8sv{}", most_recent_k8s_version).as_str())
             .expect("Cannot create new build metadata");
     let expected_policy_version = semver::Version {
-        build: build_version,
+        pre: build_version,
         ..current_policy_version.clone()
     };
 

crates/policy-version-helper/src/main.rs

@@ -213,11 +213,11 @@ annotations:
     The versioning scheme of this policy follows this pattern:
 
     ```
-    <policy version>+k8sv<most recent version of kubernes known by the embedded deprecation rules>
+    <policy version>-k8sv<most recent version of kubernes known by the embedded deprecation rules>
     ```
 
-    For example, the release `0.1.0+k8sv1.26.0` of this policy knows about all the deprecation rules
+    For example, the release `0.1.0-k8sv1.26.0` of this policy knows about all the deprecation rules
     formulated up to Kubernetes release 1.26.0.
 
     The announcement of new deprecation rules for Kubernetes 1.27.0 would trigger
-    then a release of this policy with the following version: `v0.1.1+k8sv1.27.0`.
+    then a release of this policy with the following version: `v0.1.1-k8sv1.27.0`.