Bump version and update changelog [SMAR-2514]

CHANGELOG.md

@@ -1,48 +1,67 @@
 # Changelog
 
+## [v0.7.0]
+
+### Added
+
+- Support for DbSynchronizationLeader has been added
+
+### Changed
+
+- Bumped version of sf-tenant-operator to 0.3.0
+
 ## [v0.6.0]
 
 ### Added
+
 - Added test pods supporting `helm test` command
 
 ### Changed
+
 - Bumped version of SmartFace Station to 1.22
 
 ### Breaking change
+
 - deployment of SmartFace Station is now disabled by default. To reenable previous behavior with deploying SmartFace Station please set the `station.enabled` value to `true`.
   - previous behavior with enabled SmartFace Station caused the installation of helm chart with default values to fail on validation because SmartFace Station is currently dependant on SmartFace API with enabled authentication, which in turn requires the existence of external authentication provider and correct configuration of relevant SmartFace services
 
 ## [v0.5.2]
 
 ### Changed
+
 - Bumped version of SmartFace Platform to 4.24
 
 ## [v0.5.1]
 
 ### Changed
+
 - Bumped version of SmartFace Platform and SmartFace Station
 
 ## [v0.5.0]
 
 ### Added
+
 - Support for using [minio subchart](https://github.com/bitnami/charts/tree/main/bitnami/minio) in place of S3 bucket
   - This is now default behavior of the helm chart
 - Support for using [postgresql subchart](https://github.com/bitnami/charts/tree/main/bitnami/postgresql) in place of externally managed PgSQL instance
   - This is now default behavior of the helm chart
 
 ### Breaking change
+
 - MinIO subchart is enabled and used by default. To keep using S3 bucket managed outside of this helm chart please set the `minio.enabled` value to `false` and provide configuration details via `configurations.s3`
 - Postgresql subchart is enabled and used by default. To keep using PgSQL instance managed outside of this helm chart please set the `postgresql.enabled` value to `false` and provide configuration details via `configurations.database`
 
 ## [v0.4.0]
 
 ### Added
+
 - Common labels with option to specify custom labels/annotation for objects
 - PodDisruptionBudgets for deployments that can be scaled
 - Support for custom KEDA triggers
 - Existing configmap for rabbitMQ and S3 is no longer necessary and the chart can create them from provided values, which is also the new default behavior for S3
 
 ### Breaking change
+
 - Changed default behavior for creating S3 configuration. If you like to continue managing the previously created S3 config map please use the `configurations.s3.existingConfigMapName` field. Otherwise the ConfigMap will be managed by the helm chart using the values provided in `configurations.s3`
   - The ConfigMap keys for existing config map are no longer configurable, so if you want to keep using the ConfigMap not managed by this chart then please make sure that the key match what the helm chart expects
 - Some values have had their keys changed or moved around:
@@ -57,11 +76,13 @@
 ## [v0.3.0]
 
 ### Added
+
 - Support for pushing watchlist data to edge streams via EdgeStreamsStateSynchronizer
 
 ## [v0.2.0]
 
 ### Added
+
 - Initial implementation
 - Chart can be configured to support following scenarios:
   - Lightweight Face Identification System (LFIS) - single-tenant and multi-tenant

Chart.yaml

@@ -36,6 +36,6 @@ maintainers:
 - name: Innovatrics
   url: https://www.innovatrics.com/
 
-version: 0.6.0
+version: 0.7.0
 
 appVersion: "v5_4.25.0"