Release v1.4.1

ComplianceAsCode · Apr 1, 2024 · b64e3e5 · b64e3e5
1 parent de5370b
commit b64e3e5
Show file tree

Hide file tree

Showing 6 changed files with 20 additions and 8 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -32,6 +32,17 @@ Versioning](https://semver.org/spec/v2.0.0.html).
 -
 
 
+## [1.4.1] - 2024-04-01
+
+### Fixes
+
+- [CMP-29272](https://issues.redhat.com/browse/OCPBUGS-29272) The Compliance
+  Operator will now clean up scan results when they're removed from a
+  `ScanSettingBinding`.
+- The Compliance Operator nows supports running multiple node profiles in the
+  same `ScanSettingBinding`. This makes it easier to have a single
+  `ScanSettingBinding` that contains all profiles for a benchmark.
+
 ## [1.4.0] - 2023-12-01
 
 ### Enhancements

diff --git a/bundle/manifests/compliance-operator.clusterserviceversion.yaml b/bundle/manifests/compliance-operator.clusterserviceversion.yaml
@@ -160,7 +160,7 @@ metadata:
       ]
     capabilities: Seamless Upgrades
     categories: Monitoring,Security
-    olm.skipRange: '>=0.1.17 <1.4.0'
+    olm.skipRange: '>=0.1.17 <1.4.1'
     operatorframework.io/cluster-monitoring: "true"
     operatorframework.io/suggested-namespace: openshift-compliance
     operators.openshift.io/infrastructure-features: '["disconnected", "fips", "proxy-aware"]'
@@ -174,7 +174,7 @@ metadata:
     operatorframework.io/arch.amd64: supported
     operatorframework.io/arch.ppc64le: supported
     operatorframework.io/arch.s390x: supported
-  name: compliance-operator.v1.4.0
+  name: compliance-operator.v1.4.1
   namespace: placeholder
 spec:
   apiservicedefinitions: {}
@@ -1653,4 +1653,5 @@ spec:
     name: operator
   - image: ghcr.io/complianceascode/k8scontent:latest
     name: profile
-  version: 1.4.0
+  replaces: 1.4.0
+  version: 1.4.1
diff --git a/catalog/preamble.json b/catalog/preamble.json
@@ -13,8 +13,8 @@
     "package": "compliance-operator",
     "entries": [
         {
-            "name": "compliance-operator.v1.4.0",
-            "skipRange": ">=0.1.17 <1.4.0"
+            "name": "compliance-operator.v1.4.1",
+            "skipRange": ">=0.1.17 <1.4.1"
         }
     ]
 }
diff --git a/config/manifests/bases/compliance-operator.clusterserviceversion.yaml b/config/manifests/bases/compliance-operator.clusterserviceversion.yaml
@@ -160,7 +160,7 @@ metadata:
       ]
     capabilities: Seamless Upgrades
     categories: Monitoring,Security
-    olm.skipRange: '>=0.1.17 <1.4.0'
+    olm.skipRange: '>=0.1.17 <1.4.1'
     operatorframework.io/cluster-monitoring: "true"
     operatorframework.io/suggested-namespace: openshift-compliance
     operators.openshift.io/infrastructure-features: '["disconnected", "fips", "proxy-aware"]'

diff --git a/version.Makefile b/version.Makefile
@@ -2,4 +2,4 @@
 # - 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?=1.4.0
+VERSION?=1.4.1
diff --git a/version/version.go b/version/version.go
@@ -1,5 +1,5 @@
 package version
 
 var (
-	Version = "1.4.0"
+	Version = "1.4.1"
 )