Skip to main content

Seqera Cloud v26.2.0_cycle73

Feature updates and improvements​

Monitoring​

  • Added a live task execution timeline to the run Tasks tab, showing each task's queued and running time.

Pipelines​

  • Extended the Nextflow version list back to 23.03, from a previous floor of 25.10.
  • Added the pipeline diagram declared in manifest.diagram to the launchpad pipeline details page.

Studios​

  • Added custom Studio icons, shown in the Studios list and on the Studios page.

Co-Scientist​

  • Moved the sandbox chip into the chat composer toolbar, beside the context chips.

Data lineage​

  • Made data lineage available in organization workspaces for runs on AWS compute environments.
  • Added pipeline:<name> and pipelineId:<id> qualifiers to lineage search, matching a pipeline's runs, tasks, and published files.
  • Added pipeline names to lineage search results and a See syntax tips link to the search modal.
  • Changed data lineage ingestion from SQS polling to SNS notifications and added s3:ListBucket to the lineage IAM policy; manually configured workspaces must be reconfigured.

General​

  • Added the reason an action stopped or failed to the Actions list.
  • Redesigned the Actions list as a table showing each action's source, status, last event, and creator, with usage details in a dialog.
  • Added guided empty states to list pages, naming the next step to take.

Bug fixes​

Co-Scientist​

  • Fixed a closed Co-Scientist chat reopening on page refresh.
  • Fixed the left navigation staying collapsed after closing the Co-Scientist chat.

Pipelines​

  • Fixed GitHub Redeliver not retrying an action trigger whose launch failed.

Studios​

  • Fixed Studios SSH authorization rate limiting applying across all sessions instead of per session.

General​

  • Fixed labels beyond the first 100 missing from the launch form and label search, and label assignments dropping selections not on the current page.
  • Fixed an unstable sort order that repeated or omitted labels when paging through the label list.

Fusion v2.6.7

Fusion v2.6.7 fixes a regression introduced in v2.6.6 that stopped retried tasks from starting when Fusion serves a work directory over NFS. If you run v2.6.6 in that configuration, upgrade.

How to pin this version​

fusion {
enabled = true
containerConfigUrl = 'https://fusionfs.seqera.io/releases/v2.6.7-amd64.json'
}
info

For ARM64 CPU architecture, use containerConfigUrl = 'https://fusionfs.seqera.io/releases/v2.6.7-arm64.json'.

Bug fixes​

NFS service mode​

  • Fixed retried tasks timing out with exit code 173 on every host after an interruption.
  • Fixed a work directory emptied by an earlier attempt failing to prepare.
  • Halved the storage listings needed to prepare a work directory.

Dependencies​

  • Updated build tooling and dependencies.

Upgrade notes​

  • Drop-in replacement for v2.6.6. No configuration changes required.
  • The regression affects Fusion in NFS mode on v2.6.6 only. Earlier v2.6 releases are unaffected.
  • Two limitations remain. A work directory reused without being cleaned is not swept, and leftover names can persist there. Snapshot restore in NFS mode is still under active work. Do not assume every restore path is covered.

Fusion v2.6.6

Fusion v2.6.6 fixes two Fusion Snapshots restore failures and extends Spot reclamation protection for NFS service mode to Google Cloud and Azure.

How to pin this version​

fusion {
enabled = true
containerConfigUrl = 'https://fusionfs.seqera.io/releases/v2.6.6-amd64.json'
}
info

For ARM64 CPU architecture, use containerConfigUrl = 'https://fusionfs.seqera.io/releases/v2.6.6-arm64.json'.

Bug fixes​

Fusion Snapshots​

  • Fixed snapshot restore failing for a task relaunched after its instance was reclaimed.
  • Fixed Fusion Snapshots never writing a checkpoint on Google Cloud VMs launched by Intelligent Compute.

NFS service mode​

  • Fixed tasks losing their NFS export when a Google Cloud or Azure host was reclaimed.

Dependencies​

  • Fixed CI and updated dependencies.

Upgrade notes​

  • Drop-in replacement for v2.6.5. No configuration changes required.
  • The permissions fix resolves restore failures for a task relaunched after a reclaim. Snapshot restore in NFS mode is still under active work. If you rely on snapshots, do not assume every restore path is covered.

Fusion v2.6.5

Fusion v2.6.5 fixes Fusion Snapshots restore for a task that is preempted and relaunched, and fixes renamed directories, the storage region lookup, and cache cleanup on unmount.

How to pin this version​

fusion {
enabled = true
containerConfigUrl = 'https://fusionfs.seqera.io/releases/v2.6.5-amd64.json'
}
info

For ARM64 CPU architecture, use containerConfigUrl = 'https://fusionfs.seqera.io/releases/v2.6.5-arm64.json'.

Bug fixes​

Fusion Snapshots​

  • Fixed a relaunched task not finding the checkpoint its previous attempt took.
  • Fixed a snapshot missing files from the task work directory in NFS mode.

General​

  • Fixed a renamed directory stranding files that were still uploading.
  • Added a timeout to the first lookup of a bucket region.
  • Fixed mounts never removing their working folder under the cache location.

Dependencies​

  • Updated the Go toolchain to 1.27.1.
  • Removed dead code and updated CI and dependencies.

Upgrade notes​

  • Drop-in replacement for v2.6.4. No configuration changes required.
  • The snapshot restore fix covers a task relaunched on a different instance, which is what happens when an instance is reclaimed. A task relaunched against the same still-running Fusion daemon that drained the previous attempt still fails to restore.

Seqera Cloud v26.2.0_cycle72

Breaking changes​

  • Google Batch and Google Cloud compute environments now require a VPC network when Use private address is enabled, and Google Batch also requires a subnet. Both the compute environment form and the API reject a create or update request that enables private addressing without them. Previously, the environment was accepted and failed later at pipeline launch.

Feature updates and improvements​

Compute environments​

  • Added the AWS r9gd instance family to the local NVMe list.
  • Removed the Preview badge from Seqera Compute in the compute environment platform list.

Credentials​

  • Removed the Beta notice from Azure Entra service principal credentials.
  • Added a Set up Workload Identity Federation in GCP panel to Google Workload Identity credentials, listing the values to copy into your Google Cloud project: the OpenID Connect issuer URL, the google.subject mapping that makes Cloud Audit Logs trace activity back to the acting Seqera user, and a recommended attribute condition that pins the workload identity pool to your organization and workspace. The provider, service account email, and token audience fields moved to a Connect the federated identity panel.

Pipelines​

  • Added deduplication of repeated GitHub webhook deliveries to an action, preventing a resend from launching the pipeline a second time. A delivery that cannot be recorded now returns 500, and GitHub offers the resend rather than reporting success.
  • Added an audit log record for every action firing.
  • Added a Created by column to the Actions list.
  • Grouped the action form into Details, Trigger, and Target sections. The form omits the Trigger section for GitHub and Seqera sources, which a webhook endpoint drives instead.

Bug fixes​

Compute environments​

  • Fixed Kubernetes, EKS, and GKE compute environment validation reporting every connection failure as Unexpected error while processing request, so connection timeouts, refused connections, DNS failures, TLS and certificate errors, and endpoints that are not a Kubernetes API server now each report what failed.
  • Fixed GKE cluster discovery reporting a generic 400 for revoked keys, exceeded quotas, and unreachable API endpoints instead of the underlying Google Cloud error.
  • Fixed compute environment validation reusing a cached client from a different compute environment, so correcting a field and resubmitting, or updating credentials, now validates against the new values.
  • Fixed GKE compute environments that use Workload Identity Federation failing with a 500 when reading run logs or downloading files.
  • Fixed Azure Cloud compute environment creation failing with an unexplained error when the credentials cannot read back a resource the forge has just created, so the error now names the resource and the missing read permission.
  • Fixed pipeline additions against Tower Agent compute environments intermittently failing with Timeout waiting for command response.

Studios​

  • Fixed Studios with mounted data links failing to start on Seqera Compute and on AWS Cloud, Azure Cloud, and Google Cloud compute environments.

Wave v1.38.0

Feature updates and improvements​

General​

  • Added support for an authenticating egress proxy for outbound HTTP clients via the shared lib-util-net ProxyConfig by @pditommaso in #1125
  • Changed env-var-overridable config properties to use kebab-case keys so they can be set from environment variables by @bebosudo in #1096
  • Aligned the build toolchain and runtime to Java 25 while keeping the bytecode target at Java 17 by @cristianrcv in #1077
  • Allowed the Claude review agent to submit approving PR reviews by @pditommaso in #1105
  • Refreshed the self-install documentation by @christopher-hakkaart in #1106

Dependencies​

  • Upgraded org.postgresql:postgresql to 42.7.12 (COMP-2149) by @cristianrcv in #1112
  • Upgraded io.netty:netty-bom to 4.2.17.Final (COMP-2376) by @cristianrcv in #1135
  • Upgraded the jib plugin to 3.5.4 for Java 25 class file support (COMP-2511) by @munishchouhan in #1136
  • Updated node dependency to v24.19.0 by @seqeralabs-renovate[bot] in #1111
  • Updated node dependency to v24.20.0 by @seqeralabs-renovate[bot] in #1122
  • Updated node dependency to v24.21.0 by @seqeralabs-renovate[bot] in #1134
  • Updated actions/checkout action to v4.4.0 by @seqeralabs-renovate[bot] in #1103
  • Updated actions/checkout action to v6.1.0 by @seqeralabs-renovate[bot] in #1104
  • Updated actions/setup-java action to v4.9.1 by @seqeralabs-renovate[bot] in #1108
  • Updated actions/setup-java action to v5.7.0 by @seqeralabs-renovate[bot] in #1109
  • Updated aws-actions/amazon-ecr-login action to v2.1.6 by @seqeralabs-renovate[bot] in #1102
  • Updated aws-actions/amazon-ecr-login action to v2.1.7 by @seqeralabs-renovate[bot] in #1121
  • Updated aws-actions/configure-aws-credentials action to v6.2.3 by @seqeralabs-renovate[bot] in #1110
  • Updated aws-actions/configure-aws-credentials action to v6.2.4 by @seqeralabs-renovate[bot] in #1127
  • Updated docker/login-action action to v4.6.0 by @seqeralabs-renovate[bot] in #1117
  • Updated anthropics/claude-code-action action to v1.0.191 by @seqeralabs-renovate[bot] in #1101
  • Updated anthropics/claude-code-action action to v1.0.198 by @seqeralabs-renovate[bot] in #1116
  • Updated anthropics/claude-code-action action to v1.0.206 by @seqeralabs-renovate[bot] in #1120
  • Updated anthropics/claude-code-action action to v1.0.213 by @seqeralabs-renovate[bot] in #1126
  • Updated anthropics/claude-code-action action to v1.0.219 by @seqeralabs-renovate[bot] in #1133

Bug fixes​

Container building​

  • Fixed Kubernetes builds being reported as failed on Kubernetes 1.36 and later even though the image was built and pushed (COMP-2368) by @munishchouhan in #1128
  • Fixed PATH in the Pixi Docker template so commands resolve in OCI-to-SIF converted images by @munishchouhan in #1131

General​

  • Fixed blob transfer jobs reporting success after uploading a 0-byte object by surfacing transfer errors when caching blobs (COMP-2142) by @stefanoboriero in #1100

Full changelog: https://github.com/seqeralabs/wave/compare/v1.37.0...v1.38.0

Seqera Cloud v26.2.0_cycle71

Feature updates and improvements​

Secrets​

  • Migrated the workspace and user secrets lists to the shared row-card table already used by compute environments and credentials. Edit and Delete moved into the row's kebab menu, and the whole row opens the edit form for users with update permission.

Bug fixes​

Credentials​

  • Fixed the inline credentials form in compute environment creation offering fewer options than the Credentials page. AWS supports role-based credentials with external ID generation, Google supports Workload Identity Federation, and Azure uses the same credential fields as that page.
  • Fixed the row actions column reserving an empty strip in the compute environment and credentials lists for users without permission to act on the row.
  • Fixed the credentials kebab menu opening an empty panel for users without permission to act on the row.

Pipelines​

  • Fixed lineage resolution for resumed runs. Each run in a resume chain now shows its own Lineage ID, instead of every run in the chain showing the most recently indexed one. A resumed run shows - while it executes, then its own Lineage ID once it completes.

Fusion v2.6.4

Fusion v2.6.4 adds retryable and non-retryable exit codes for startup failures in NFS service mode, and new health and liveness metrics. It also fixes renamed directories and very large files on Google Cloud Storage.

How to pin this version​

fusion {
enabled = true
containerConfigUrl = 'https://fusionfs.seqera.io/releases/v2.6.4-amd64.json'
}
info

For ARM64 CPU architecture, use containerConfigUrl = 'https://fusionfs.seqera.io/releases/v2.6.4-arm64.json'.

Feature updates and improvements​

NFS service mode​

  • Added distinct exit codes for startup failures when Fusion runs as the NFS daemon and cannot complete its startup handshake with the control node. Fusion exits with 172 when the control node rejects the request, which is a configuration or permission problem that a retry cannot fix. Fusion exits with 173 for anything else, such as an unreachable or slow control node, and for ambiguous failures. Intelligent Compute relocates the task on 173 instead of aborting the run. See Exit codes 172 and 173.
  • Added FUSION_NFS_READINESS_TIMEOUT to set how long Fusion waits for its work directory to become ready before it classifies the failure and exits. The default is 60 seconds.

Metrics​

  • Added the fusion_health_* metric family to the per-task metrics file. It reports uptime, memory use split into non-overlapping categories, open file handles, cache device disk usage, mount initialization time, and shutdown flush time. Resource exhaustion is now visible after the fact.
  • Added two liveness gauges that report how many file system requests are outstanding and the age of the oldest one. The age stays near zero when nothing is calling Fusion and climbs when Fusion has taken a request and not answered it. Use them to tell a stalled mount from an idle one.
  • Published a schema and triage runbook for the metrics file. See Fusion task metrics.

Bug fixes​

General​

  • Fixed a renamed directory dropping files and symlinks that were not yet uploaded.
  • Fixed a "no such file" error on NFS daemon clusters for an input produced by another task.
  • Fixed a retried task starting on leftovers from the previous attempt.
  • Fixed .tbi, .csi, and .bai index files appearing older than the data they index.
  • Fixed symlink targets longer than 2048 bytes being truncated on read.
  • Fixed declared outputs with adjacent brace patterns being evicted at shutdown instead of persisted.
  • Fixed a truncate or seek-write to an implausible offset exhausting memory and killing the mount, which is now rejected with a clear error.
  • Fixed temporary files being uploaded while the task was still writing them, except on runs with snapshots enabled.

Google Cloud​

  • Fixed corrupt results for very large files on Google Cloud Storage, roughly 128 GiB and above at the default chunk size.
  • Added a check that rejects an object over the 5 TiB Google Cloud Storage per-object limit before uploading.

Dependencies​

  • Reorganized the metrics collector, added a streaming upload endpoint on the control interface, and moved fusion-tracer onto it.
  • Updated CI, build pipeline, and dependencies.

Upgrade notes​

  • Drop-in replacement for v2.6.3. No configuration changes required.
  • In NFS mode, fusion-tracer now sends its trace through the control interface and no longer falls back to writing it through the mount. A trace produced while the control node is unreachable is dropped. Tracing is unchanged when the control node is reachable.
  • FUSION_NFS_READINESS_TIMEOUT is new and defaults to 60 seconds.

Seqera Cloud v26.2.0_cycle70

Feature updates and improvements​

Compute environments​

  • Grouped compute environment selects by platform, listed the workspace primary environment first, and added an in-panel search that matches on name, region, and platform.
  • Changed the pre-selected compute environment in launch forms from the alphabetically first environment to the workspace primary environment.

General​

  • Removed the count badges from the Runs, Reports, Datasets, and Projects tabs.

Bug fixes​

Credentials​

  • Fixed the Password field helper text on the GitLab and Gitea credential forms to state that a personal access token must be entered in both the Access token and Password fields, and that the Password field is required for Nextflow versions before 26.04.

Pipelines​

  • Fixed the launch form to preserve the output directory when resuming a run, instead of publishing to the pipeline default.
  • Fixed user-typed launch parameters being discarded when a config profile or revision change re-fetched the parameters.
  • Fixed schema default parameters being dropped from the submitted parameters after selecting a config profile.
  • Fixed nested parameter groups being submitted as null, which disabled Launch with no way to clear the error.

Seqera Cloud v26.2.0_cycle69

Feature updates and improvements​

Studios​

  • Added filtering to the Studios list, with the selected filters persisted across navigation.

Compute environments​

  • Added an OS disk size setting to Azure Cloud compute environments.
  • Added an optional Region field to the Azure credential forms, with autocomplete suggestions and free-text entry for regions outside the catalog.

Pipelines​

  • Added support for Nextflow v26.08.0-edge.
  • Improved launch performance by reducing the number of SCM calls made on the launch path.

Data Explorer​

  • Added search to the data link selector in the bucket action form.

Bug fixes​

Compute environments​

  • Fixed false "region not found" warnings on Azure credentials by probing Azure Batch in the credential's own region instead of westeurope, and by validating Batch access on the compute environment rather than the credential.
  • Fixed compute environment deletion being possible while creation was still in progress.
  • Fixed the compute environment details page to redirect to the compute environment list after a deletion.
  • Fixed forged Azure Cloud compute environments losing their Nextflow configuration.
  • Fixed runs being flagged for attention when a UserData script failed.

Credentials​

  • Fixed credential validation to back off and escalate probes that fail permanently, instead of retrying them at the same rate.

Monitoring and observability​

  • Fixed the runs toolbar disappearing in loading and empty states.

Credits​

  • Fixed the credits report download to show progress and offer a cancel control.

General​

  • Fixed the default workspace preference not being cleared correctly.