add note about updating metadata.yaml

Signed-off-by: kranurag7 <[email protected]>

Author: kranurag7

docs/develop/releasing.md

@@ -2,6 +2,9 @@
 This document describes the release process of cluster-stack-operator. 
 The release process is done using GitHub actions. The release workflow triggers when a tag is pushed starting with `v*` 
 
+> [!NOTE]
+> Before the release, please make sure that you've already updated metadata.yaml at the root of the repo. So, if you're using v1.2.0 then you'll also need to update the `releaseSeries` block in metadata.yaml. The tag used for releasing should be compatible with what we have defined in metadata.yaml
+
 Creating a new release of cluster-stack-operator covers the following steps: 
 
 ### Step 1: Create and Push a tag 
@@ -30,4 +33,4 @@ This will automatically trigger a Github workflow to create a draft release in G
 > [!WARNING]
 > :rotating_light: This is a RELEASE CANDIDATE. If you find any bugs, please file an [issue](https://github.com/SovereignCloudStack/cluster-stack-operator/issues/new).
 3. Before publishing the images make sure that images are already there in GitHub container registry. This can be checked in the [packages section](https://github.com/SovereignCloudStack/cluster-stack-operator/pkgs/container/cso) of the organisation.
-4. Publish the release.
+4. Publish the release.