Dbeaver devops#2868 release 26 2 0

.env.example

@@ -1,4 +1,4 @@
-CLOUDBEAVER_VERSION_TAG=26.1.0
+CLOUDBEAVER_VERSION_TAG=26.2.0
 IMAGE_SOURCE=dbeaver
 PODMAN_IMAGE_SOURCE=docker.io/dbeaver
 COMPOSE_PROJECT_NAME=dbeaver

AWS/ecs-fargate/variables.tf.example

@@ -25,7 +25,7 @@ variable "cloudbeaver_image_name" {
 variable "cloudbeaver_version" {
   description = "The version of the cluster you want to deploy"
   type = string
-  default = "26.1.0"
+  default = "26.2.0"
 }
 
 variable "alb_certificate_Identifier" {
@@ -138,4 +138,4 @@ variable "cloudbeaver-db-env" {
     { "name": "POSTGRES_DB",
      "value": "cloudbeaver"}
   ]
-}
+}

README.md

@@ -1,6 +1,6 @@
 # CloudBeaver Enterprise deployment
 
-### Version 26.1
+### Version 26.2
 
 CloudBeaver Enterprise is a client-server application.
 It requires server deployment. You can deploy it in several ways:
@@ -14,7 +14,7 @@ It requires server deployment. You can deploy it in several ways:
 It is the simplest way to install [CloudBeaver Enterprise Edition](https://dbeaver.com/cloudbeaver-enterprise/).  
 All you need is a Linux, macOS, or Windows machine with Docker.
 
-CloudBeaver can be run in a [single docker container](#installation-with-docker-image).  
+CloudBeaver can be run in a [single docker container](#installation-with-docker-image).
 However you can use Docker compose for easy web server (HTTPS) configuration.
 
 ### System requirements
@@ -173,9 +173,13 @@ podman-compose -f podman-compose.yml up -d
 or replace `docker-compose.yml` with `podman-compose.yml` and use `podman-compose` without compose project definition
 
 ### Updating the cluster
-1. Replace the value of `CLOUDBEAVER_VERSION_TAG` in `.env` with a preferred version. If you use the tag `latest`, you don't need to do anything during this step.
-2. Pull new docker images: `docker-compose pull` or `docker compose pull`
-3. Restart the cluster: `docker-compose up -d` or `docker compose up -d`
+1. Stop the cluster: `docker-compose down` or `docker compose down`.
+2. Update your deployment files:
+   - Fetch the latest changes: `git fetch`.
+   - Switch to the branch for the version you're updating to: `git checkout <version>` (for example, `git checkout 26.2.0`).
+3. Replace the value of `CLOUDBEAVER_VERSION_TAG` in `.env` with the preferred version. Skip this step if the tag is set to `latest`.
+4. Pull new Docker images: `docker-compose pull` or `docker compose pull`.
+5. Start the cluster: `docker-compose up -d` or `docker compose up -d`.
 
 ## Installation with Docker image
 
@@ -234,11 +238,12 @@ Previously, the volumes were owned by the ‘root’ user, but now they’re own
 ## Older versions
 
 ### Older versions:
+- [26.1.0](https://github.com/dbeaver/cloudbeaver-deploy/tree/26.1.0)
 - [26.0.0](https://github.com/dbeaver/cloudbeaver-deploy/tree/26.0.0)
 - [25.3.0](https://github.com/dbeaver/cloudbeaver-deploy/tree/25.3.0)
 - [25.2.0](https://github.com/dbeaver/cloudbeaver-deploy/tree/25.2.0)
 - [25.1.0](https://github.com/dbeaver/cloudbeaver-deploy/tree/25.1.0)
 - [25.0.0](https://github.com/dbeaver/cloudbeaver-deploy/tree/25.0.0)
 - [24.3.0](https://github.com/dbeaver/cloudbeaver-deploy/tree/24.3.0)
 - [24.2.0](https://github.com/dbeaver/cloudbeaver-deploy/tree/24.2.0)
-- [24.1.0](https://github.com/dbeaver/cloudbeaver-deploy/tree/24.1.0)
+- [24.1.0](https://github.com/dbeaver/cloudbeaver-deploy/tree/24.1.0)

k8s/Chart.yaml

@@ -3,4 +3,4 @@ name: cb
 description: A Helm chart for CloudBeaver application
 type: application
 version: 0.0.1
-appVersion: 26.1.0
+appVersion: 26.2.0

k8s/README.md

@@ -38,11 +38,14 @@ Previously, the volumes were owned by the ‘root’ user, but now they are owne
     Private Key: `ingressSsl/privkey.pem`
 - Deploy Cloudbeaver with Helm: `helm install cloudbeaver ./ --values ./values.yaml`
 
-### Version update procedure.
-
-- Change directory to `cloudbeaver-deploy/k8s`.
-- Change value of `imageTag` in configuration file `values.yaml` with a preferred version. Go to next step if tag `latest` set.
-- Upgrade cluster: `helm upgrade cloudbeaver ./ --values ./values.yaml` 
+### Version update procedure
+
+1. Change directory to `cloudbeaver-deploy/k8s`.
+2. Update your deployment files:
+   - Fetch the latest changes: `git fetch`.
+   - Switch to the branch for the version you're updating to: `git checkout <version>` (for example, `git checkout 26.2.0`).
+3. Change the value of `imageTag` in the `values.yaml` configuration file to the preferred version. Skip this step if the tag is set to `latest`.
+4. Upgrade the cluster: `helm upgrade cloudbeaver ./ --values ./values.yaml`.
 
 ### OpenShift deployment
 

k8s/values.yaml.example

@@ -6,7 +6,7 @@
 cloudbeaver:
   replicaCount: 1
   image: dbeaver/cloudbeaver-ee
-  imageTag: "26.1.0"
+  imageTag: "26.2.0"
   pullPolicy: Always
   # pullCredsName - name of a secret config map that contains docker repo auths
   # pullCredsName: regcred