Changelog
Wave v1.9.0
Feature updates and improvements
Container building
- Bumped BuildKit to 0.14.0 by @munishchouhan in https://github.com/seqeralabs/wave/pull/528
- Bumped BuildKit to 0.14.1 by @pditommaso in https://github.com/seqeralabs/wave/pull/548
- Removed build logs AWS config to not initialize
AwsS3Operationsby @munishchouhan in https://github.com/seqeralabs/wave/pull/558
Spack
- Deprecated the support for Spack and remove the support for it in the codebase by @munishchouhan in https://github.com/seqeralabs/wave/pull/550
API
- Updated metrics response by @munishchouhan in https://github.com/seqeralabs/wave/pull/536
- Refactored metrics 2 by @munishchouhan in https://github.com/seqeralabs/wave/pull/549
- Added Typespec API definitions by @munishchouhan in https://github.com/seqeralabs/wave/pull/537
Performance
- Added
record-statsby @munishchouhan in https://github.com/seqeralabs/wave/pull/534 - Checked and deleted corrupted blobs in cache by @munishchouhan in https://github.com/seqeralabs/wave/pull/533
General
- Added
troubleshootby @munishchouhan in https://github.com/seqeralabs/wave/pull/529 - Updated Wave docs to include licensing note by @justinegeffen in https://github.com/seqeralabs/wave/pull/557
- Improved container credentials retrieval using workflow compute environment by @munishchouhan in https://github.com/seqeralabs/wave/pull/303
Bug fixes
Performance
- Fixed client cache deadlock by @pditommaso in https://github.com/seqeralabs/wave/pull/547
General
- Fixed multiple S3Clients in Wave by @munishchouhan in https://github.com/seqeralabs/wave/pull/554
- Fixed null storage bucket error in build logs by @munishchouhan in https://github.com/seqeralabs/wave/pull/555
- Fixed failing test by @munishchouhan in https://github.com/seqeralabs/wave/pull/539
New Contributors
- @justinegeffen made their first contribution in https://github.com/seqeralabs/wave/pull/557
Full changelog: https://github.com/seqeralabs/wave/compare/v1.8.2...v1.9.0
Seqera Enterprise v24.1
Seqera Platform Enterprise version 24.1 introduces three new features: Data Studios (in public preview), Data Explorer, and managed identities. A number of bug fixes and performance enhancements are included in this major release.
Feature updates and improvements
Data Studios
Data Studios closes the loop from development to deployment and insights, allowing you to create, manage, and share notebook environments in Seqera with the click of a button. Data Studios makes it seamless to work across teams with multi-user support, built-in authentication, and automatic snapshots as you work.
- Host a combination of container images and compute environments for interactive analysis using your preferred tools, like Jupyter notebooks, RStudio, and Visual Studio Code IDEs.
- 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 to request access to this feature.
Data Explorer
Data Explorer allows you to browse and interact with remote data repositories from organization workspaces in Seqera Platform. It supports AWS S3, Azure Blob Storage, and Google Cloud Storage repositories.
Data Explorer is now Generally Available (GA) and supports multi-file and multi-folder download. This allows users to download entire datasets of pipeline results to share with their team.
Extended data roles
User roles provide flexibility for admins to provide users with the permissions they need, without compromising security. The Connect user role has been added to the existing user roles with functionality related to Data Studios:
- Connect: Open a connection to a running data studio session and interact with the contents.
- Maintain: Create, update, start, stop, configure, and delete data studio sessions.
- View: List, search, and view the status, configuration, and details of data studios.
- Launch: Open a connection to a running data studio session and interact with the contents.
See User roles for more information.
Managed identities
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 for more information.
Other feature improvements
- A redesigned pipeline launch form 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.
- Retrieve reports from primary compute environment on Nextflow CLI runs. See Configure reports for Nextflow CLI runs for more information.
- The standard email login can be disabled via
tower.ymlor an environment variable, provided an alternative OIDC provider is set up first. See Basic configuration for more information.
Breaking changes
MariaDB driver: New MySQL connection parameter required
MariaDB driver 3.x requires a special parameter in the connection URL to connect to a MySQL database:
jdbc:mysql://<domain>:<port>/tower?permitMysqlScheme=true
All deployments using a MySQL database (regardless of version: 5.6, 5.7, or 8) should be updated accordingly when upgrading to Platform version 24.1 or later.
MariaDB driver: No truncation support for MySQL 5.6
The MariaDB driver has dropped support for the jdbcCompliantTruncation parameter, which was true by default and set the STRICT_TRANS_TABLES SQL mode. The STRICT_TRANS_TABLES mode produces an error when the value of a VARCHAR column exceeds its limit, instead of truncating it to fit. Most common installations of MySQL 5.7 and 8 already include this mode at the server level, but the Docker container version of MySQL 5.6 does not.
The SQL mode must be set explicitly through the connection URL for deployments still using MySQL 5.6:
jdbc:mysql://<domain>:<port>/tower?permitMysqlScheme=true&sessionVariables=sql_mode='STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION'
Micronaut property key changes
The property that determines the expiration time of the JWT access token (used for authenticating web sessions and Nextflow-Platform interactions) has changed:
| 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
- This version includes an update to the Platform Enterprise H8 cache. Do not start the upgrade while any pipelines are in a
runningstate as active run data may be lost. - This version requires a database schema update. Make a backup of your Platform database prior to upgrade.
- If you are upgrading from a version older than 23.4.1, update your installation to version 23.4.4 first, before updating to 24.1 with the steps below.
- For recommended Platform memory settings, add the following environment variable to your Platform configuration values (
tower.env,configmap.yml, etc.):JAVA_OPTS: -Xms1000M -Xmx2000M -XX:MaxDirectMemorySize=800m -Dio.netty.maxDirectMemory=0 -Djdk.nio.maxCachedBufferSize=262144 - See Upgrade installation for database backup and installation upgrade guidance.
Docker Compose deployments require downtime while upgrading services. Restarting the application may take several minutes. See Docker compose deployment 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 for more information.
For custom deployments with third-party services such as ArgoCD, contact support for assistance during upgrade.
Seqera Enterprise v24.1.1
Feature updates and improvements
Data Studios
- Added the ability to rename data studio checkpoints.
Data Explorer
- Added OpenAPI support for Data Explorer.
- Show loading in Workflow/Task Data Explorer tab while waiting for data link cache refresh.
General
- Datasets can now be used in personal workspaces.
- Pipeline secrets can now be used in personal workspaces.
Compute environments
- Added Graviton3 EC2 instance family as valid NVMe instance types.
- Added new G6 EC2 instance family as valid NVMe instance types.
- Deprecated EBS autoscale in the Seqera Platform user interface.
Workflows
- Retrieve reports from primary compute environment on NF CLI runs.
- At nf-launcher, propagate a curl failures and exit.
Security updates
Infrastructure
- Upgraded base Docker images to get upstream updates.
Version bump
Infrastructure
- Bumped nf-launcher:j17-23.10.1-up1
Wave v1.8.3
Feature updates and improvements
Performance
- Added cache
record-statsby @pditommaso in https://github.com/seqeralabs/wave/pull/534
Bug fixes
Performance
- Fixed client cache deadlock by @pditommaso in https://github.com/seqeralabs/wave/pull/547
Full changelog: https://github.com/seqeralabs/wave/compare/v1.8.2...v1.8.3
Wave v1.8.2
Bug fixes
General
- Fixed get image auth digest by @pditommaso in https://github.com/seqeralabs/wave/pull/530
Full changelog: https://github.com/seqeralabs/wave/compare/v1.8.1...v1.8.2
Wave v1.8.1
Feature updates and improvements
API
- Updated metrics API documentation by @munishchouhan in https://github.com/seqeralabs/wave/pull/523
Bug fixes
General
- Fixed image name strategy by @munishchouhan in https://github.com/seqeralabs/wave/pull/513
- Fixed digest warning by @pditommaso in https://github.com/seqeralabs/wave/pull/526
Full changelog: https://github.com/seqeralabs/wave/compare/v1.8.0...v1.8.1
Wave v1.8.0
Feature updates and improvements
Container building
- Implemented cache store for build records by @pditommaso in https://github.com/seqeralabs/wave/pull/505
- Replaced kaniko with BuildKit by @munishchouhan in https://github.com/seqeralabs/wave/pull/503
API
- Added breakdown per org on stats metrics when a date is specified by @munishchouhan in https://github.com/seqeralabs/wave/pull/517
General
- Added
homebrew installdocumentation by @munishchouhan in https://github.com/seqeralabs/wave/pull/514
Bug fixes
General
- Fixed minor typos by @mribeirodantas in https://github.com/seqeralabs/wave/pull/515
- Fixed handling blob response headers by @pditommaso in https://github.com/seqeralabs/wave/pull/504
- Fixed metric key pattern variable name by @munishchouhan in https://github.com/seqeralabs/wave/pull/518
New Contributors
- @mribeirodantas made their first contribution in https://github.com/seqeralabs/wave/pull/515
Full changelog: https://github.com/seqeralabs/wave/compare/v1.7.9...v1.8.0
Wave v1.7.9
Feature updates and improvements
API
- Updated API documentation by @munishchouhan in https://github.com/seqeralabs/wave/pull/464
- Improved JWT refresh handling by @pditommaso in https://github.com/seqeralabs/wave/pull/512
General
- Removed unused imports by @munishchouhan in https://github.com/seqeralabs/wave/pull/510
- Clean up metrics docs by @jason-seqera in https://github.com/seqeralabs/wave/pull/508
Bug fixes
General
- Fixed rate limit docs by @munishchouhan in https://github.com/seqeralabs/wave/pull/506
Full changelog: https://github.com/seqeralabs/wave/compare/v1.7.8...v1.7.9