Skip to main content

Seqera Enterprise v25.3.3

Feature updates and improvements​

Studios​

  • (Public preview) Added SSH connectivity to Studios which enables direct connection to running Studio sessions using standard SSH clients, supporting VS Code Remote SSH and terminal access. See Studios SSH configuration for more information.

Pipelines​

  • Added custom schema support to pipeline versions.
  • Added edit launch pipeline.
  • Enabled custom schema retrieval for pipeline versions.

See Pipeline versioning for more information.

Access Control​

  • Removed participants on workspace deletion.
  • Improved error message when deleting custom roles.
  • Added pagination to roles list page.
  • Added the ability to view an effective permissions summary for any user/workspace combination in the UI or via API.
  • Added the ability to reset a custom role's permissions to match any predefined role (Admin, Maintain, Launch, Connect, View).

Custom roles quota enforcement​

The maxCustomRolesPerOrg quota is now enforced on custom role creation. Organizations at or near their quota limit will be unable to create additional custom roles. Review your organization's custom role usage if you need to create additional roles. Contact support to adjust your quotas if needed.

General​

  • Restored custom navigation menu support in user dropdown.
  • Updated styles for container responsiveness and padding adjustments and footer.
  • Added only current page in task pagination.
  • Added storage for SSH public keys for use in Studios.

Bug fixes​

  • Cleared parameters when changing between pipeline with and without parameters.
  • Fixed correctly updated versions list when version is published.
  • Prevented re-assignations of pipeline.launch when working with versions.
  • Updated schema when schemaName field value changes.
  • Prevented adding empty parameters when reseting parameters form with defaults after config profile change.

Upgrade steps​

This release maintains backward compatibility with version 25.2.x.

note
  • Make a backup of your Platform database prior to upgrade.
  • If you are upgrading from a version prior to 25.1, complete all intermediate major version upgrades before upgrading to 25.3.
  • Ensure that no pipelines or Studio sessions are in a running state during this upgrade as active run data and analysis may be lost.

See Upgrade deployment for installation guidance.

On this Page