Skip to content

Changelog for Seqera Cloud cycle 7 #561

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Apr 25, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions changelog/seqera-cloud/25.1.0_cycle7.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
---
title: Seqera Cloud v25.1.0_cycle7
date: 2025-04-23
tags: [seqera cloud]
---

### 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.
Loading