Update values on values.yaml too, as only updating appVersion isn't e…

…nough (#32)

Co-authored-by: Jussi Liukkonen <[email protected]>

charts/geoweb-frontend/Chart.yaml

@@ -15,7 +15,7 @@ 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.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 3.0.4
+version: 3.0.5
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to

charts/geoweb-frontend/README.md

@@ -103,7 +103,7 @@ The following table lists the configurable parameters of the GeoWeb frontend cha
 
 | Parameter | Description | Default |
 | - | - | - |
-| `versions.frontend` | Possibility to override application version | `v8.0.0` |
+| `versions.frontend` | Possibility to override application version | `v8.2.0` |
 | `frontend.name` | Name of frontend | `geoweb` |
 | `frontend.registry` | Registry to fetch image | `registry.gitlab.com/opengeoweb/opengeoweb` |
 | `frontend.commitHash` | Adds commitHash annotation to the deployment | |

charts/geoweb-frontend/values.yaml

@@ -1,5 +1,5 @@
 versions:
-  frontend: "v8.0.0"
+  frontend: "v8.2.0"
 
 frontend:
   name: geoweb

charts/geoweb-opmet-backend/Chart.yaml

@@ -15,7 +15,7 @@ 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.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 2.3.4
+version: 2.3.5
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to

charts/geoweb-opmet-backend/README.md

@@ -57,7 +57,7 @@ The following table lists the configurable parameters of the Opmet backend chart
 
 | Parameter | Description | Default |
 | - | - | - |
-| `versions.opmet` | Possibility to override application version | `v1.2.0` |
+| `versions.opmet` | Possibility to override application version | `v1.3.0` |
 | `opmet.name` | Name of backend | `opmet` |
 | `opmet.registry` | Registry to fetch image | `registry.gitlab.com/opengeoweb/backend-services/opmet-backend` |
 | `opmet.commitHash` | Adds commitHash annotation to the deployment | |

charts/geoweb-opmet-backend/values.yaml

@@ -1,5 +1,5 @@
 versions:
-  opmet: "v1.2.0"
+  opmet: "v1.3.0"
 
 opmet:
   name: opmet

charts/geoweb-presets-backend/Chart.yaml

@@ -15,7 +15,7 @@ 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.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 2.5.3
+version: 2.5.4
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to

charts/geoweb-presets-backend/README.md

@@ -78,7 +78,7 @@ The following table lists the configurable parameters of the Presets backend cha
 
 | Parameter | Description | Default |
 | - | - | - |
-| `versions.presets` | Possibility to override application version | `3.5.2` |
+| `versions.presets` | Possibility to override application version | `3.5.4` |
 | `presets.name` | Name of backend | `presets` |
 | `presets.registry` | Registry to fetch image | `registry.gitlab.com/opengeoweb/backend-services/presets-backend` |
 | `presets.commitHash` | Adds commitHash annotation to the deployment | |

charts/geoweb-presets-backend/values.yaml

@@ -1,5 +1,5 @@
 versions:
-  presets: "3.5.2"
+  presets: "3.5.4"
 
 presets:
   name: presets