Skip to main content

Seqera Cloud v27.1.0_cycle79

Feature updates and improvements​

Studios​

  • Added recovery of a Studio's last checkpoint when it was not saved completely, with an option to undo the recovery.
  • Added starting a new Studio from a checkpoint that was not saved completely.
  • Changed the recommended Xpra Studio template to 6.5.4 and marked the previous 6.3.6 template as deprecated.

Compute environments​

  • Added Spot VMs to the worker pool of an Azure Batch Forge compute environment that uses separate head and worker pools. The head pool always uses dedicated VMs.
  • Added pinned instance types to an AWS Batch Forge work queue when Fusion Snapshots is enabled and Instance types is empty.
  • Renamed the Allowed S3 buckets field to Additional S3 buckets on AWS Batch, AWS Cloud, and Seqera Compute compute environments.
  • Clarified the AWS CLI path helper text on AWS Batch compute environments.

Credentials​

  • Added an optional repository path to the Registry server of a container registry credential, so a credential can be scoped to a single repository.
  • Changed new AWS credentials to start in Role mode on Seqera Cloud.
  • Redesigned the credentials list as a table with columns for name, ID, last updated, last activity, and status.

Secrets​

  • Redesigned the secrets list as a table with columns for name, last updated, and last activity.

Data Explorer​

  • Added creating an empty folder on AWS S3, Google Cloud Storage, and Azure Blob Storage data links, in Data Explorer and in the data picker of the launch form.

Service accounts​

  • Added Access and Authentication tabs to the service account details page.
  • Added a Studio SSH key to a service account, which an organization owner can view and delete from the Authentication tab.

Co-Scientist​

  • Replaced the sandbox chip above the chat message box with a sandbox label and a Download sandbox contents icon below it.
  • Redesigned the conversation history with Chats and Agent sessions tabs, organization groups, and search.

Monitoring​

  • Added pipelineId: to the search suggestions on the runs list.

General​

  • Added outbound request protection in enforcing mode, which refuses requests to Git servers and other destinations you supply that resolve to private or link-local addresses.
  • Removed the credentials of a request from a Git server redirect that changes host, port, or scheme.

Bug fixes​

Compute environments​

  • Fixed Azure Batch Forge pools keeping container storage on the managed OS disk, which failed tasks with ContainerInvalidSettings.
  • Fixed a running Azure Cloud run being marked as failed after a single head VM poll returned no power state.
  • Fixed a Google Cloud run whose head VM was already deleted ending as unknown with an empty error report instead of failed.
  • Fixed the duplicate compute environment page showing the copy name in place of a page title.
  • Fixed an AWS compute environment form keeping an AMI ID from the previous region after the region changed.
  • Fixed AWS Cloud reporting a failed setup script on instance types that have no instance store NVMe disks.
  • Fixed job submission stalling for other runs when a compute environment's SSH host accepted a connection but never responded.

Credentials​

  • Fixed a GitHub App credential authenticating as the wrong installation when the app is installed on more than one account.

Data Explorer​

  • Fixed adding an Azure data repository with invalid credentials reporting a bucket validation error instead of a credentials error.

Data lineage​

  • Fixed lineage links failing to resolve in large workspaces because the lookup of a record's run timed out.
  • Fixed lineage run and task links not opening in a new tab, and not supporting middle-click, cmd-click, or Copy link.

Monitoring​

  • Fixed the run details page keeping the previous run on screen after navigating to another run.
  • Fixed empty logs, empty log downloads, and a reports tab stuck on Reports are generating when a run's files cannot be read over SSH.

Pipelines​

  • Fixed launches failing with a Wave service connection error during a routine reconnect of the Wave pairing.
  • Fixed a launch that adds resource labels reporting a data error instead of naming the role limit.
  • Fixed a Git repository that Platform cannot reach reporting an unexpected error instead of naming the repository and the reason.

Agents​

  • Fixed an agent launch being reported as failed while the agent backend continued and queued the run.
On this Page