docs: Add redirect and versioned links

changelog/seqera-enterprise/v23.4.md

@@ -65,7 +65,7 @@ A previous iteration of the rebranded Seqera documentation noted `seqera` as the
 
 **ARM64 CPU architecture support enabled by default**
 
-The **Use Graviton CPU architecture** option is now available by default during AWS Batch compute environment creation. The `TOWER_ENABLE_ARM64` configuration environment variable is no longer needed to enable ARM64 CPU architecture support. 
+The **Use Graviton CPU architecture** option is now available by default during AWS Batch compute environment creation. The `TOWER_ENABLE_ARM64` configuration environment variable is no longer needed to enable ARM64 CPU architecture support.
 
 **Data Explorer default set to `false`**
 
@@ -122,4 +122,4 @@ If you must host your nf-launcher container image on a private image registry, c
 If you're using AWS Batch, you will need to [configure a custom job definition](https://docs.seqera.io/platform-enterprise/23.4/enterprise/advanced-topics/custom-launch-container) and populate the `TOWER_LAUNCH_CONTAINER` with the job definition name instead.
 :::
 
-[gcp-vm-instance-template]: https://cloud.google.com/compute/docs/instance-templates
+[gcp-vm-instance-template]: https://cloud.google.com/compute/docs/instance-templates

changelog/seqera-enterprise/v24.1.md

@@ -43,7 +43,7 @@ See [Managed identities](https://docs.seqera.io/platform-cloud/credentials/manag
 
 - 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/enterprise/configuration/overview#basic-configuration) 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/24.1/enterprise/configuration/overview#basic-configuration) for more information.
 
 ## Breaking changes
 
@@ -85,9 +85,9 @@ Enterprise deployments that have customized this value previously will need to a
 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/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/24.1/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/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/24.1/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.
 :::

changelog/seqera-enterprise/v25.1.md

@@ -6,15 +6,15 @@ tags: [seqera enterprise]
 
 Seqera Platform Enterprise version 25.1 introduces Studios GA and a number of bug fixes and performance enhancements.
 
-Studios is Seqera's in-platform tool for secure, on-demand, interactive data analysis using containers created from Seqera-managed container template images or your own organization-managed custom environments. You only pay for the compute your Studio sessions consume, and the compute is adjacent to your data, significantly reducing data transfer costs and wasted time copying data from storage to analysis. This significantly reduces infrastructure management requirements, removes data silos, adheres to strict in-platform role-based access control, and lowers your operational costs. [Learn more about Studios](https://docs.seqera.io/platform-enterprise/studios).
+Studios is Seqera's in-platform tool for secure, on-demand, interactive data analysis using containers created from Seqera-managed container template images or your own organization-managed custom environments. You only pay for the compute your Studio sessions consume, and the compute is adjacent to your data, significantly reducing data transfer costs and wasted time copying data from storage to analysis. This significantly reduces infrastructure management requirements, removes data silos, adheres to strict in-platform role-based access control, and lowers your operational costs. [Learn more about Studios](https://docs.seqera.io/platform-enterprise/25.1/studios/overview).
 
 ## New features and improvements
 
 ### Studios
 
 - **Labeled templates**: Labels indicate the status of support (`recommended` or `deprecated`) for a Seqera-managed Studio container template version. Users can migrate a Studio to a new base container template when **Adding as new**.
-- **[Private sessions](https://docs.seqera.io/platform-enterprise/studios/managing#general-config)**: When adding a new Studio, the number of concurrent connections (private vs. all workspace members) can now be defined in **General Config > Collaboration**.
-- **[Custom session lifespans](https://docs.seqera.io/platform-enterprise/studios/managing#modify-session-lifespan-for-all-studios)**: This new feature allows you to set a maximum lifespan for a session, after which time the session is stopped automatically and a checkpoint created, or the session can be extended on-demand.
+- **[Private sessions](https://docs.seqera.io/platform-enterprise/25.1/studios/managing#general-config)**: When adding a new Studio, the number of concurrent connections (private vs. all workspace members) can now be defined in **General Config > Collaboration**.
+- **[Custom session lifespans](https://docs.seqera.io/platform-enterprise/25.1/studios/managing#modify-session-lifespan-for-all-studios)**: This new feature allows you to set a maximum lifespan for a session, after which time the session is stopped automatically and a checkpoint created, or the session can be extended on-demand.
 - **Resource labels**: Users with at least workspace maintainer role permissions can manage the resource labels inherited from the compute environment and attached to the Studio. Resource labels attached to each Studio don’t affect the default resource labels associated with the compute environment.
 
 ### Fusion
@@ -138,9 +138,9 @@ Upgrading to version 25.1 requires backend downtime in order for the database mi
 1. See [Upgrade installation](https://docs.seqera.io/platform-enterprise/24.2/enterprise/upgrade) for 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/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/25.1/enterprise/docker-compose) for more information.
 
-For Kubernetes deployments, apply the 25.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 Kubernetes deployments, apply the 25.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/25.1/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.
 :::