From 744d3a1448ab1651eeeae80de36cf89f9a42e94b Mon Sep 17 00:00:00 2001 From: Justine Geffen Date: Fri, 9 Oct 2026 21:08:35 +0200 Subject: [PATCH 1/9] Update proxy image version to 0.13.0 Update minimum recommended version to 0.13.0. Signed-off-by: Justine Geffen --- .../enterprise/_templates/k8s/data_studios/proxy.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/platform-enterprise_versioned_docs/version-26.1/enterprise/_templates/k8s/data_studios/proxy.yml b/platform-enterprise_versioned_docs/version-26.1/enterprise/_templates/k8s/data_studios/proxy.yml index 89cfa4d108..dbe4d59922 100644 --- a/platform-enterprise_versioned_docs/version-26.1/enterprise/_templates/k8s/data_studios/proxy.yml +++ b/platform-enterprise_versioned_docs/version-26.1/enterprise/_templates/k8s/data_studios/proxy.yml @@ -19,7 +19,7 @@ spec: kubernetes.io/arch: amd64 containers: - name: proxy - image: cr.seqera.io/enterprise/studios/proxy:0.11.0 + image: cr.seqera.io/enterprise/studios/proxy:0.13.0 env: - name: CONNECT_HTTP_PORT value: "8081" From 821ac2f2b7c84570164013632492edc9e9c41d2f Mon Sep 17 00:00:00 2001 From: Justine Geffen Date: Fri, 9 Oct 2026 21:09:54 +0200 Subject: [PATCH 2/9] Update Studios proxy and server image versions Signed-off-by: Justine Geffen --- .../enterprise/_templates/docker/docker-compose.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/platform-enterprise_versioned_docs/version-26.1/enterprise/_templates/docker/docker-compose.yml b/platform-enterprise_versioned_docs/version-26.1/enterprise/_templates/docker/docker-compose.yml index 926cd91237..d956d6dc57 100644 --- a/platform-enterprise_versioned_docs/version-26.1/enterprise/_templates/docker/docker-compose.yml +++ b/platform-enterprise_versioned_docs/version-26.1/enterprise/_templates/docker/docker-compose.yml @@ -122,7 +122,7 @@ services: # Uncomment the following section to enable Studios functionality. See [Studios configuration](../../../studios/overview) for more information. # connect-proxy: -# image: cr.seqera.io/enterprise/studios/proxy:0.11.0 +# image: cr.seqera.io/enterprise/studios/proxy:0.13.0 # platform: linux/amd64 # env_file: # - data-studios.env @@ -138,7 +138,7 @@ services: # - $HOME/.tower/connect:/data # # connect-server: -# image: cr.seqera.io/enterprise/studios/server:0.11.0 +# image: cr.seqera.io/enterprise/studios/server:0.13.0 # platform: linux/amd64 # env_file: # - data-studios.env From 2eeaff5a8cff4265edc8b055f449385b05d8b4eb Mon Sep 17 00:00:00 2001 From: Justine Geffen Date: Fri, 9 Oct 2026 21:11:07 +0200 Subject: [PATCH 3/9] Update server.yml Signed-off-by: Justine Geffen --- .../enterprise/_templates/k8s/data_studios/server.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/platform-enterprise_versioned_docs/version-26.1/enterprise/_templates/k8s/data_studios/server.yml b/platform-enterprise_versioned_docs/version-26.1/enterprise/_templates/k8s/data_studios/server.yml index 9dd68e001b..24a9e772c9 100644 --- a/platform-enterprise_versioned_docs/version-26.1/enterprise/_templates/k8s/data_studios/server.yml +++ b/platform-enterprise_versioned_docs/version-26.1/enterprise/_templates/k8s/data_studios/server.yml @@ -21,7 +21,7 @@ spec: kubernetes.io/arch: amd64 containers: - name: server - image: cr.seqera.io/enterprise/studios/server:0.11.0 + image: cr.seqera.io/enterprise/studios/server:0.13.0 ports: - containerPort: 7070 name: server From 62e90914319dd966873dc05780aa505759114215 Mon Sep 17 00:00:00 2001 From: Justine Geffen Date: Fri, 9 Oct 2026 21:17:36 +0200 Subject: [PATCH 4/9] Update upgrade.md Signed-off-by: Justine Geffen --- platform-enterprise_docs/enterprise/upgrade.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/platform-enterprise_docs/enterprise/upgrade.md b/platform-enterprise_docs/enterprise/upgrade.md index 9992de0f37..3405f8b46a 100644 --- a/platform-enterprise_docs/enterprise/upgrade.md +++ b/platform-enterprise_docs/enterprise/upgrade.md @@ -10,12 +10,10 @@ Upgrade your Seqera Platform Enterprise installation and database to version 26. :::info[**Prerequisites**] -You need the following: - -- A backup of your Platform database. -- Each intermediate major version upgrade complete, if you're upgrading from a version earlier than 25.1. For example, upgrade from 24.1 to 25.1, then to 26.1, then to 26.2. The following sections list the requirements for each version. -- No pipelines running during the upgrade. Data from active runs can be lost. - +- Make a backup of your Platform database. +- Complete each intermediate major version upgrade if you're upgrading from a version earlier than 25.1. For example, upgrade from 24.1 to 25.1, then to 26.1, then to 26.2. The sections below list the requirements for each version. +- Make sure no pipelines are running during the upgrade. Data from active runs can be lost. +- Make sure no Studios are running. Active Studios with mounted data can be irreparably damaged. ::: ## Upgrade from versions earlier than 24.1 From fe9c9e9fabf24aa55559affe92023945999d4cdd Mon Sep 17 00:00:00 2001 From: Justine Geffen Date: Fri, 9 Oct 2026 21:18:52 +0200 Subject: [PATCH 5/9] Add upgrade prerequisites for version 25.1 Added prerequisites for upgrading to version 25.1, including backup and ensuring no active pipelines or Studios. Signed-off-by: Justine Geffen --- .../version-25.1/enterprise/upgrade.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/platform-enterprise_versioned_docs/version-25.1/enterprise/upgrade.md b/platform-enterprise_versioned_docs/version-25.1/enterprise/upgrade.md index 23103e4cbb..a088df45dd 100644 --- a/platform-enterprise_versioned_docs/version-25.1/enterprise/upgrade.md +++ b/platform-enterprise_versioned_docs/version-25.1/enterprise/upgrade.md @@ -11,6 +11,13 @@ Follow these steps to upgrade your database instance and Platform Enterprise ins From Seqera Enterprise version 23.4, MySQL 8 is the only supported database version. If you are upgrading from a version prior to 23.4 and running MySQL 5.6 or 5.7, you must upgrade your database to MySQL 8 before upgrading to version 25.1. See [General upgrade steps](#general-upgrade-steps) for database upgrade instructions. ::: +:::info[**Prerequisites**] + +- Make a backup of your Platform database. +- Make sure no pipelines are running during the upgrade. Data from active runs can be lost. +- Make sure no Studios are running. Active Studios with mounted data can be irreparably damaged. +::: + ### General upgrade steps :::caution From 2f2c26b97ed71be1617f67a7d8d3c0d61a1f4db4 Mon Sep 17 00:00:00 2001 From: Justine Geffen Date: Fri, 9 Oct 2026 21:19:32 +0200 Subject: [PATCH 6/9] Revise upgrade.md with prerequisites and warnings Updated upgrade instructions to include prerequisites and clarify steps for database backup and running pipelines. Signed-off-by: Justine Geffen --- .../version-25.2/enterprise/upgrade.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/platform-enterprise_versioned_docs/version-25.2/enterprise/upgrade.md b/platform-enterprise_versioned_docs/version-25.2/enterprise/upgrade.md index 3c8fddaf6d..0029312742 100644 --- a/platform-enterprise_versioned_docs/version-25.2/enterprise/upgrade.md +++ b/platform-enterprise_versioned_docs/version-25.2/enterprise/upgrade.md @@ -7,10 +7,12 @@ tags: [enterprise, update, installation] This page outlines the steps to upgrade your database instance and Platform Enterprise installation to version 25.2, including special considerations for upgrading from versions prior to 25.1. -:::note -- Make a backup of your Platform database prior to upgrade. -- If you are upgrading from a version prior to 25.1, complete all intermediate major version upgrades before upgrading to 25.2. -- Ensure that no pipelines are in a running state during this upgrade as active run data may be lost. +:::info[**Prerequisites**] + +- Make a backup of your Platform database. +- Complete each intermediate major version upgrade if you're upgrading from a version earlier than 25.1. The sections below list the requirements for each version. +- Make sure no pipelines are running during the upgrade. Data from active runs can be lost. +- Make sure no Studios are running. Active Studios with mounted data can be irreparably damaged. ::: ### Considerations for versions prior to 24.1 From 6b04c4a61914a159a7ff2f52fe82924844d1f436 Mon Sep 17 00:00:00 2001 From: Justine Geffen Date: Fri, 9 Oct 2026 21:20:05 +0200 Subject: [PATCH 7/9] Update upgrade.md Signed-off-by: Justine Geffen --- .../version-25.3/enterprise/upgrade.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/platform-enterprise_versioned_docs/version-25.3/enterprise/upgrade.md b/platform-enterprise_versioned_docs/version-25.3/enterprise/upgrade.md index 17033e8f29..5bef0e4edb 100644 --- a/platform-enterprise_versioned_docs/version-25.3/enterprise/upgrade.md +++ b/platform-enterprise_versioned_docs/version-25.3/enterprise/upgrade.md @@ -7,10 +7,12 @@ tags: [enterprise, update, installation] This page outlines the steps to upgrade your database instance and Platform Enterprise installation to version 25.3, including special considerations for upgrading from versions prior to 25.1. -:::note -- Make a backup of your Platform database prior to upgrade. -- If you are upgrading from a version prior to 25.1, complete all intermediate major version upgrades before upgrading to 25.3. -- Ensure that no pipelines are in a running state during this upgrade as active run data may be lost. +:::info[**Prerequisites**] + +- Make a backup of your Platform database. +- Complete each intermediate major version upgrade if you're upgrading from a version earlier than 25.1. The sections below list the requirements for each version. +- Make sure no pipelines are running during the upgrade. Data from active runs can be lost. +- Make sure no Studios are running. Active Studios with mounted data can be irreparably damaged. ::: ### Considerations for versions prior to 24.1 From eb64ef363d3130f9b1e33df07e60d1ce9a103d0d Mon Sep 17 00:00:00 2001 From: Justine Geffen Date: Fri, 9 Oct 2026 21:21:25 +0200 Subject: [PATCH 8/9] Update upgrade.md Signed-off-by: Justine Geffen --- .../version-26.1/enterprise/upgrade.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/platform-enterprise_versioned_docs/version-26.1/enterprise/upgrade.md b/platform-enterprise_versioned_docs/version-26.1/enterprise/upgrade.md index d2d0bf75ff..947e5bee8c 100644 --- a/platform-enterprise_versioned_docs/version-26.1/enterprise/upgrade.md +++ b/platform-enterprise_versioned_docs/version-26.1/enterprise/upgrade.md @@ -8,10 +8,12 @@ tags: [enterprise, update, installation] This page outlines the steps to upgrade your database instance and Platform Enterprise installation to version 26.1, including special considerations for upgrading from earlier versions. -:::note -- Make a backup of your Platform database prior to upgrade. -- If you are upgrading from a version prior to 25.1, complete all intermediate major version upgrades before upgrading to 26.1, for example from 23.1 upgrade to 24.1, then 25.1, and finally 26.1. More specific requirements are detailed below for each major version. -- Ensure that no pipelines are in a running state during this upgrade as active run data may be lost. +:::info[**Prerequisites**] + +- Make a backup of your Platform database. +- Complete each intermediate major version upgrade if you're upgrading from a version earlier than 25.1. For example, upgrade from 23.1 to 24.1, then to 25.1, then to 26.1. The sections below list the requirements for each version. +- Make sure no pipelines are running during the upgrade. Data from active runs can be lost. +- Make sure no Studios are running. Active Studios with mounted data can be irreparably damaged. ::: ## Upgrading from versions prior to 24.1 From be34b201759b59d8f911f3af76f2a4a45d94c10c Mon Sep 17 00:00:00 2001 From: Justine Geffen Date: Fri, 9 Oct 2026 21:21:50 +0200 Subject: [PATCH 9/9] Update upgrade prerequisites for version 26.2 Revised prerequisites for upgrading to version 26.2, clarifying backup and upgrade path requirements. Signed-off-by: Justine Geffen --- .../version-26.2/enterprise/upgrade.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/platform-enterprise_versioned_docs/version-26.2/enterprise/upgrade.md b/platform-enterprise_versioned_docs/version-26.2/enterprise/upgrade.md index 9992de0f37..65bf3b0119 100644 --- a/platform-enterprise_versioned_docs/version-26.2/enterprise/upgrade.md +++ b/platform-enterprise_versioned_docs/version-26.2/enterprise/upgrade.md @@ -10,12 +10,10 @@ Upgrade your Seqera Platform Enterprise installation and database to version 26. :::info[**Prerequisites**] -You need the following: - -- A backup of your Platform database. -- Each intermediate major version upgrade complete, if you're upgrading from a version earlier than 25.1. For example, upgrade from 24.1 to 25.1, then to 26.1, then to 26.2. The following sections list the requirements for each version. -- No pipelines running during the upgrade. Data from active runs can be lost. - +- Make a backup of your Platform database. +- Complete each intermediate major version upgrade if you're upgrading from a version earlier than 25.1. For example, upgrade from 23.1 to 24.1, then to 25.1, then to 26.1. The sections below list the requirements for each version. +- Make sure no pipelines are running during the upgrade. Data from active runs can be lost. +- Make sure no Studios are running. Active Studios with mounted data can be irreparably damaged. ::: ## Upgrade from versions earlier than 24.1