Add release governance and version consistency checks

.github/workflows/publish-helm-charts.yml

@@ -22,6 +22,44 @@ jobs:
         with:
           fetch-depth: 0
 
+      - name: Check chart versions
+        run: |
+          echo "## Checking Chart Versions"
+
+          # Get versions
+          PROD_VERSION=$(grep "^version:" charts/opencloud/Chart.yaml | awk '{print $2}')
+          DEV_VERSION=$(grep "^version:" charts/opencloud-dev/Chart.yaml | awk '{print $2}')
+
+          echo "- opencloud: $PROD_VERSION"
+          echo "- opencloud-dev: $DEV_VERSION"
+
+          # Basic semver check (x.y.z format)
+          for version in "$PROD_VERSION" "$DEV_VERSION"; do
+            if ! [[ "$version" =~ ^[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
+              echo "❌ ERROR: Version '$version' is not valid semver"
+              exit 1
+            fi
+          done
+
+          # Check tag consistency if this is a tag push
+          if [[ "$GITHUB_REF" == refs/tags/v* ]]; then
+            TAG_VERSION="${GITHUB_REF#refs/tags/v}"
+            echo ""
+            echo "## Publishing for tag: v$TAG_VERSION"
+
+            # Check if tag matches chart versions
+            if [ "$PROD_VERSION" != "$TAG_VERSION" ] && [ "$DEV_VERSION" != "$TAG_VERSION" ]; then
+              echo "⚠️ WARNING: Tag doesn't match any chart version"
+              echo "  Both charts will be updated from their current versions to $TAG_VERSION"
+            elif [ "$PROD_VERSION" = "$TAG_VERSION" ] && [ "$DEV_VERSION" != "$TAG_VERSION" ]; then
+              echo "⚠️ Dev chart will be updated from $DEV_VERSION to $TAG_VERSION"
+            elif [ "$DEV_VERSION" = "$TAG_VERSION" ] && [ "$PROD_VERSION" != "$TAG_VERSION" ]; then
+              echo "⚠️ Production chart will be updated from $PROD_VERSION to $TAG_VERSION"
+            else
+              echo "✅ Both charts already at version $TAG_VERSION"
+            fi
+          fi
+
       - name: Set up Helm
         uses: azure/setup-helm@v3
         with:

CONTRIBUTING.md

@@ -41,6 +41,30 @@ When making changes, please ensure you:
 - Ensure your PR has a clear description of the changes
 - At least one reviewer must approve before a maintainer can merge
 
+## Release Process
+
+### Creating a Release
+
+Only maintainers can create releases. The process is:
+
+1. **Update versions**: Update the version in all Chart.yaml files
+2. **Update documentation**: Add release notes to CHANGELOG.md (if exists)
+3. **Create PR**: Submit a PR with the version changes
+4. **Tag after merge**: After the PR is merged, create and push a tag:
+   ```bash
+   git tag -a v0.x.x -m "Release v0.x.x"
+   git push origin v0.x.x
+   ```
+
+### Version Guidelines (0.x.x phase)
+
+During the initial development phase (0.x.x), we follow these conventions:
+- `0.x.0` - Breaking changes (incompatible API/values changes)
+- `0.x.y` - New features (backwards compatible)
+- `0.x.y-z` - Bug fixes only
+
+Note: As per [SemVer 2.0](https://semver.org/spec/v2.0.0.html#spec-item-4), the 0.x.x range indicates the API is not stable and breaking changes may occur.
+
 ## Code of Conduct
 
 This project follows the [Contributor Covenant Code of Conduct](https://www.contributor-covenant.org/version/2/1/code_of_conduct/).