Skip to main content

Changelog

Seqera Cloud v25.2.0_cycle15

General updates and improvements

  • aborted status task counts are now included in progress response when a workflow is finalized.
  • Improvement to launch parameters handling after revision/config profiles are changed, and existing parameters are now completely overridden during a revision or config profile change.
  • Filtering by workspaceId when downloading credits usage CSV file is now supported.

Seqera Cloud v25.2.0_cycle14

New features and improvements

  • Studios
    • Added Conda helper text to the Conda packages field in Add new Studio > General config.
    • Added CONNECT_CE parameter to activate Spot reclamation watcher in the Connect client.
  • Fusion
    • Added P5, P5e, P6-b200, I7i, C8gd, M8gd and R8gd EC2 families that support NVMe disk. Learn more on the AWS What's New page.
  • Updated the PLUGIN_LIST environment variable for Nextflow 25.04.x to include the K8s plugin when needed.

Bug fixes

  • Fixed an issue where removed/modified parameters were persisting on pipeline relaunch.

Seqera Cloud v25.1.0_cycle10 - cycle12

Seqera Compute

Seqera Compute is now in public preview. Seqera Compute is a fully managed, optimized compute environment which eliminates infrastructure complexity by automating environment setup, resource provisioning, scaling, and optimization.

Platform interface updates

Pipeline run details

The pipeline run details page has been refreshed and includes improvements such as:

  • Clear, dynamic view of pipeline execution in real time via a progress bar.
  • A dedicated Run info tab with a centralized view of run metadata and status details.
  • Improved navigation tabs for Tasks, Logs, Metrics, and Containers.

New Seqera Platform sidebar

The Platform top navigation has been replaced with a sidebar for improved navigation.

AWS Cloud compute environment

The new AWS Cloud compute environment supports faster startup time, simplified configuration, and fewer AWS dependencies. Using this compute environment, Studios can now be launched on Spot instances. The AWS Cloud compute environment is best suited to run Studios and small to medium-sized pipelines. It offers more predictable compute pricing, given the fixed instance type. It spins up a standalone EC2 instance and executes a Nextflow pipeline or Studio session with a local executor on the EC2 machine. At the end of the execution, the instance is terminated.

API documentation improvements

The Seqera Platform API documentation has been updated. Featuring overview pages with parameter and request body tables, categorized by Platform entity (compute environments, pipelines, etc.), the documentation now provides easier reference and detailed request examples.

Other new features and improvements

  • Fusion
  • Studios
    • Add Spot option for AWS Cloud compute environment.
  • Support markdown rendering for Nextflow object field help_text and description properties.
note

This changelog includes releases

  • v25.1.0-cycle10_37f83e6
  • v25.1.0-cycle11_cde3ebf
  • v25.1.0-cycle11_0ff195a
  • v25.1.0-cycle12_3d9ec0c
  • v25.1.0-cycle12_8bf53cd
  • v25.1.0-cycle12_c98e9a5
  • v25.1.0-cycle12_1d46e0f
  • v25.1.0-cycle12_61865f4
  • v25.1.0-cycle12_fbec4ef
  • v25.1.0-cycle12_20df528

Seqera Cloud v25.1.0_cycle9

Feature updates and improvements

  • Fusion
    • Add Fusion Snapshots support in AWS Batch compute environments, enabling Fusion to automatically restore jobs interrupted by AWS Spot instance reclamation. See Fusion Snapshots for more information.

Bug fixes

  • Fix container table pagination.
  • Make task-level containers tab visible only when containers are available.
  • Fix a launch form issue with eager parameter keyword interpolation.

Seqera Cloud v25.1.0_cycle7

Feature updates and improvements

  • Data Explorer
    • You can now drag and drop multiple folders or files to upload them to your cloud bucket, or you can select Upload, then select multiple files to upload.
  • Fusion:
    • The Seqera-optimized AMI is now the default for the single VM compute environment. If no AMI is specified when adding a compute environment, it defaults to the Seqera-optimized AMI.
  • Add a more detailed warning for workflow cleanup issues that are related to access restrictions to the AWS Batch compute environment.
  • Add support for array type parameters in the Launch form.
  • Implement support for multiple extension dataset parameters in the input form.
  • Delete pipeline secrets in the user context from the provider.
  • Switch logs, secrets-manager, marketplace-meter, and simple-email dependencies to AWS SDK v2.
  • Show Nextflow config parameters that are binary expressions in the Launch form.
  • Add azure_entra to the provider list of credentials in the OpenAPI spec.
  • Switch AWS S3 to SDK v2.
  • Add task status badges with icons to the workflow run tasks table.

Bug fixes

  • Modify cache expiration policy to resolve "Connection pool shut down" error with new AWS SDK v2 clients.
  • Fix an issue where the workflow details page displays the Edit Labels button even when there are no labels, but resource labels are attached to the workflow.
  • Fix an issue where the Quick Launch form did not select the primary compute environment by default.

Seqera Enterprise v25.2.5

General

This release backports the default Azure image fix from v25.1.1 to v24.2.x:

Azure Batch support for Ubuntu 20.04 LTS ending

The default Azure Batch Ubuntu image has been updated with sku 22.04. This is to ensure there are no issues with the existing Azure Batch Ubuntu image (sku 20.04) which will be deprecated after April 23, 2025. See, https://github.com/Azure/Batch/issues/174 for more information about the deprecation.

Seqera Enterprise v25.1.1

General

  • Azure Batch support for Ubuntu 20.04 LTS ending: The default Azure Batch Ubuntu image has been updated with sku 22.04. This is to ensure there are no issues with the existing Azure Batch Ubuntu image (sku 20.04) which will be deprecated after April 23, 2025. See, https://github.com/Azure/Batch/issues/174 for more information about the deprecation.
  • Implement support for multiple extension dataset parameters in the input form.