seqeralabs · gavinelder · May 11, 2025 · May 11, 2025 · May 11, 2025 · May 15, 2025
diff --git a/changelog/seqera-enterprise/v22.4.md b/changelog/seqera-enterprise/v22.4.md
@@ -5,7 +5,7 @@ tags: [seqera enterprise]
 ---
 
 :::note
-The documentation for v22.4 is no longer supported. These release notes are for reference only. 
+The documentation for v22.4 is no longer supported. These release notes are for reference only.
 :::
 
 ## New features
@@ -65,7 +65,7 @@ The only requirement is that the new compute environment has access to the origi
 
 ### Warnings
 
-1. The default `nf-launcher` image includes a `curl` command which will fail if your Tower is secured with a private TLS certificate. To mitigate this problem, please see [these instructions](https://docs.seqera.io/platform-enterprise/latest/enterprise/configuration/ssl_tls).
+1. The default `nf-launcher` image includes a `curl` command which will fail if your Tower is secured with a private TLS certificate. To mitigate this problem, please see [these instructions](https://docs.seqera.io/platform-enterprise/enterprise/configuration/ssl_tls).
 2. This version requires all database connections to use the following configuration value: `TOWER_DB_DRIVER=org.mariadb.jdbc.Driver`. Please update your configuration if you are upgrading. All other database configuration values should remain unchanged.
 3.  This version expects the use of HTTPS by default for all browser client connections. If your Tower installation requires the use of unsecured HTTP, set the following environment variable in the infrastructure hosting the Tower application: `TOWER_ENABLE_UNSAFE_MODE=true`.
 4.  If you're upgrading from a version of Tower prior to `21.04.x`, please update your implementation to `21.04.x` before installing this release.
@@ -102,7 +102,7 @@ If you must host your nf-launcher container image on a private image registry, c
     `TOWER_LAUNCH_CONTAINER=<FULL_PATH_TO_YOUR_PRIVATE_IMAGE>`
 
 !!! warning
-    If you're using AWS Batch, you will need to [configure a custom job definition](https://docs.seqera.io/platform-enterprise/latest/enterprise/advanced-topics/custom-launch-container) and populate the `TOWER_LAUNCH_CONTAINER` with the job definition name instead.
+    If you're using AWS Batch, you will need to [configure a custom job definition](https://docs.seqera.io/platform-enterprise/enterprise/advanced-topics/custom-launch-container) and populate the `TOWER_LAUNCH_CONTAINER` with the job definition name instead.
 
 ## Sharing feedback
 

diff --git a/changelog/seqera-enterprise/v23.2.md b/changelog/seqera-enterprise/v23.2.md
@@ -95,7 +95,7 @@ If you must host your nf-launcher container image on a private image registry:
     `TOWER_LAUNCH_CONTAINER=<FULL_PATH_TO_YOUR_PRIVATE_IMAGE>`
 
 !!! warning ""
-    If you're using AWS Batch, you will need to [configure a custom job definition](https://docs.seqera.io/platform-enterprise/latest/enterprise/advanced-topics/custom-launch-container) and populate the `TOWER_LAUNCH_CONTAINER` with the job definition name instead.
+    If you're using AWS Batch, you will need to [configure a custom job definition](https://docs.seqera.io/platform-enterprise/enterprise/advanced-topics/custom-launch-container) and populate the `TOWER_LAUNCH_CONTAINER` with the job definition name instead.
 
 ## Sharing feedback
 

diff --git a/changelog/seqera-enterprise/v23.3.md b/changelog/seqera-enterprise/v23.3.md
@@ -117,6 +117,6 @@ If you must host your nf-launcher container image on a private image registry, c
     `TOWER_LAUNCH_CONTAINER=<FULL_PATH_TO_YOUR_PRIVATE_IMAGE>`
 
 :::caution
-If you're using AWS Batch, you will need to [configure a custom job definition](https://docs.seqera.io/platform-enterprise/latest/enterprise/advanced-topics/custom-launch-container) and populate the `TOWER_LAUNCH_CONTAINER` with the job definition name instead.
+If you're using AWS Batch, you will need to [configure a custom job definition](https://docs.seqera.io/platform-enterprise/enterprise/advanced-topics/custom-launch-container) and populate the `TOWER_LAUNCH_CONTAINER` with the job definition name instead.
 :::
 
diff --git a/changelog/seqera-enterprise/v24.1.8.mdx b/changelog/seqera-enterprise/v24.1.8.mdx
diff --git a/changelog/seqera-enterprise/v24.1.md b/changelog/seqera-enterprise/v24.1.md
@@ -14,7 +14,7 @@ Seqera Platform Enterprise version 24.1 introduces three new features: Data Stud
 - Checkpoints provide a stable point-in-time snapshot.
 - Collaborate and share data in real time.
 
-Data Studios is available as a public preview. [Contact support](https://support.seqera.io) to request access to this feature. 
+Data Studios is available as a public preview. [Contact support](https://support.seqera.io) to request access to this feature.
 
 ## Data Explorer
 
@@ -37,13 +37,13 @@ See [User roles](https://docs.seqera.io/platform-cloud/orgs-and-teams/roles) for
 
 Managed identities offer significant advantages for High-Performance Computing (HPC) environments by enabling granular access control for individual workspace users. Unlike traditional SSH credentials that grant all workspace users access to HPC clusters with the same service account, managed identities ensure each user’s activity is logged under their own credentials.
 
-See [Managed identities](https://docs.seqera.io/platform-cloud/credentials/managed_identities) for more information. 
+See [Managed identities](https://docs.seqera.io/platform-cloud/credentials/managed_identities) for more information.
 
 ## Other feature improvements
 
 - A redesigned [pipeline launch form](https://docs.seqera.io/platform-cloud/getting-started/quickstart-demo/launch-pipelines) provides an improved workflow and an interface to create and edit run parameters as raw JSON/YAML. Enable the new launch form per workspace via [environment variable](https://docs.seqera.io/platform-enterprise/24.2/enterprise/configuration/overview#core-features).
-- Retrieve reports from primary compute environment on Nextflow CLI runs. See [Configure reports for Nextflow CLI runs](https://docs.seqera.io/platform-cloud/reports/overview#configure-reports-for-nextflow-cli-runs) for more information. 
-- The standard email login can be disabled via `tower.yml` or an environment variable, provided an alternative OIDC provider is set up first. See [Basic configuration](https://docs.seqera.io/platform-enterprise/latest/enterprise/configuration/overview#basic-configuration) for more information.
+- Retrieve reports from primary compute environment on Nextflow CLI runs. See [Configure reports for Nextflow CLI runs](https://docs.seqera.io/platform-cloud/reports/overview#configure-reports-for-nextflow-cli-runs) for more information.
+- The standard email login can be disabled via `tower.yml` or an environment variable, provided an alternative OIDC provider is set up first. See [Basic configuration](https://docs.seqera.io/platform-enterprise/enterprise/configuration/overview#basic-configuration) for more information.
 
 ## Breaking changes
 
@@ -70,27 +70,27 @@ The property that determines the expiration time of the JWT access token (used f
 | Previous                                                         | New                                                          |
 | ---------------------------------------------------------------- | ------------------------------------------------------------ |
 | `micronaut.security.token.jwt.generator.access-token.expiration` | `micronaut.security.token.generator.access-token.expiration` |
-	
+
 Enterprise deployments that have customized this value previously will need to adopt the new format.
 
-## Upgrade steps 
+## Upgrade steps
 
 1. This version includes an update to the Platform Enterprise H8 cache. **Do not start the upgrade while any pipelines are in a `running` state as active run data may be lost.**
 1. This version requires a database schema update. Make a backup of your Platform database prior to upgrade.
 1. If you are upgrading from a version older than 23.4.1, update your installation to version [23.4.4](https://docs.seqera.io/changelog/seqera-enterprise/v23.4) first, before updating to 24.1 with the steps below.
 1. For recommended Platform memory settings, add the following environment variable to your Platform configuration values (`tower.env`, `configmap.yml`, etc.):
-    ```bash 
+    ```bash
     JAVA_OPTS: -Xms1000M -Xmx2000M -XX:MaxDirectMemorySize=800m -Dio.netty.maxDirectMemory=0 -Djdk.nio.maxCachedBufferSize=262144
     ```
 1. See [Upgrade installation](https://docs.seqera.io/platform-enterprise/24.2/enterprise/upgrade) for database backup and installation upgrade guidance.
 
 :::info
-Docker Compose deployments require downtime while upgrading services. Restarting the application may take several minutes. See [Docker compose deployment](https://docs.seqera.io/platform-enterprise/latest/enterprise/docker-compose) for more information.
+Docker Compose deployments require downtime while upgrading services. Restarting the application may take several minutes. See [Docker compose deployment](https://docs.seqera.io/platform-enterprise/enterprise/docker-compose) for more information.
 
-For Kubernetes deployments, apply the 24.1 `tower-cron.yml` to your cron pod and wait for the cron pod to be running before applying the `tower-svc.yml` to your backend pod and restarting the service. If the cron pod update is interrupted, you may need to restore the instance from your DB backup and start again. See [Kubernetes deployment](https://docs.seqera.io/platform-enterprise/latest/enterprise/kubernetes) for more information. 
+For Kubernetes deployments, apply the 24.1 `tower-cron.yml` to your cron pod and wait for the cron pod to be running before applying the `tower-svc.yml` to your backend pod and restarting the service. If the cron pod update is interrupted, you may need to restore the instance from your DB backup and start again. See [Kubernetes deployment](https://docs.seqera.io/platform-enterprise/enterprise/kubernetes) for more information.
 
-For custom deployments with third-party services such as ArgoCD, [contact support](https://support.seqera.io) for assistance during upgrade. 
-::: 
+For custom deployments with third-party services such as ArgoCD, [contact support](https://support.seqera.io) for assistance during upgrade.
+:::
 
 
 [gcp-vm-instance-template]: https://cloud.google.com/compute/docs/instance-templates