Bump version to 19.0.0 for 18-stable release

Author: ospk8s-branching-bot[bot]

.github/workflows/build-openstack-operator.yaml

@@ -16,7 +16,7 @@ jobs:
       go_version: 1.26.x
       operator_sdk_version: 1.42.3
       bundle_dockerfile: ./bundle.Dockerfile
-      operator_version: 0.7.0
+      operator_version: 19.0.0
     secrets:
       IMAGENAMESPACE: ${{ secrets.IMAGENAMESPACE }}
       QUAY_USERNAME: ${{ secrets.QUAY_USERNAME }}

.github/workflows/catalog-openstack-operator-upgrades.yaml

@@ -63,9 +63,9 @@ jobs:
         run: ./openstack-operator/hack/catalog-build-olm-upgrade.sh
         env:
           #FIXME: these should be pulled from a YAML config in the main operator directory?
-          MAIN_VERSION: 0.7.0
-          FEATURE_RELEASE_VERSION: 0.6.0
-          FEATURE_RELEASE_BRANCH: 18.0-fr6
+          MAIN_VERSION: 19.0.0
+          FEATURE_RELEASE_VERSION: 0.7.0
+          FEATURE_RELEASE_BRANCH: 18-stable
           BUNDLE: ${{ env.imageregistry }}/${{ env.imagenamespace }}/openstack-operator-bundle:${{ github.sha }}
       - name: Buildah Action
         id: build-operator-index-upgrade

Makefile

@@ -3,7 +3,7 @@
 # To re-generate a bundle for another specific version without changing the standard setup, you can:
 # - use the VERSION as arg of the bundle target (e.g make bundle VERSION=0.0.2)
 # - use environment variables to overwrite this value (e.g export VERSION=0.0.2)
-VERSION ?= 0.7.0
+VERSION ?= 19.0.0
 
 OPENSTACK_RELEASE_VERSION ?= $(VERSION)-$(shell date +%s)
 

hack/fake_minor_update.sh

@@ -1,7 +1,7 @@
 # A quick way to test a fake minor update. Run this script, and then once the
 # openstackversion reconciles (the CSV will redeploy the controller-manager)
 # you can set targetVersion == 0.0.2 for a quick test
-VERSION=0.7
+VERSION=19.0
 CURRENT=${VERSION}.0
 UPDATE=${VERSION}.1
 oc get csv openstack-operator.v${CURRENT} -o yaml -n openstack-operators  > csv.yaml