Seqera Enterprise v26.1.6
Bug fixes
Platform API
- Fixed generated API clients and schema validators rejecting valid
2xxresponses. Optional credential, pipeline, workflow, task, team, participant, user, and organization response properties are now declared nullable in the OpenAPI specification. Runtime serialization is unchanged. - Fixed compute environment responses failing schema validation. Nullable AWS Batch, Forge, and common compute configuration fields are now declared, forged and deleted Forge resources are modelled as string-valued maps, and
ForgeConfig.arm64Enabled,ForgeConfig.fargateHeadEnabled, andsecretsKmsKeyIdare nullable when a persisted configuration omits them. - Fixed credential responses emitting
nullAWS and GitHub secret values. Null secrets are now omitted from the JSON response while write-only OpenAPI semantics are retained, and the conditionalworkspaceIdrequirement for workspace-owned versus user-owned credentials is documented. - Fixed the workflow, task, load, statistics, launch, and job response contracts to match the values actually returned, and corrected
LogPage.entriesto an array of strings. - Fixed the pipeline version creator metadata, repository list values, and the dataset, participant, data-link, label, and Studios response contracts to match the values actually returned.
- Fixed dataset downloads losing the stored media type, and declared CSV, TSV, and octet-stream response media types for dataset version downloads.
- Fixed the GA4GH WES endpoints returning
500instead of404for a run ID that does not exist. Run describe, status, and cancel now return and document404, and member lookup documents404.
Monitoring and observability
- Fixed
fusion_throughput_bytestelemetry reporting only the first day of the current month for each organization. The current month now counts every day so far. Past months are unchanged.
General
- Fixed the Fusion throughput quota never blocking a launch. The launch-time check read the current month's usage as zero because usage is stored as one row per day, so
maxFusionThroughputByteswas never enforced. The check now sums the organization's daily rows for the current UTC month, which matches the figure shown on the Fusion usage dashboard.
Upgrade notes
No breaking changes. Standard upgrade procedure applies. No database migrations are included in this release.
API changes
The published API contract moves from 1.184.0 to 1.192.0. Most changes correct the specification to describe responses the server already returned, with two exceptions that change responses:
- Null credential secrets are now omitted. AWS and GitHub secret keys that previously serialized as
nullare no longer present in credential responses. Clients that read these keys must tolerate an absent key rather than anullvalue. - GA4GH WES returns
404for unknown runs. Run describe, status, and cancel return404instead of500when the run ID does not exist.
Regenerate any OpenAPI-derived clients against 1.192.0 to pick up the corrected nullability declarations.
Behavior changes
- The Fusion throughput quota is now enforced. Organizations with
maxFusionThroughputBytesset have had no effective limit since Fusion usage moved to daily rows. Launches that exceed the configured quota are now blocked. Review configured quotas against current Fusion usage before you upgrade. - Fusion telemetry totals increase. The
fusion_throughput_bytesvalue reported for the current month now covers the full month to date rather than its first day.
Security updates
- CVE-2026-42198: Updated the PostgreSQL JDBC driver to 42.7.12, which resolves a client-side denial of service during SCRAM-SHA-256 authentication, where a malicious server requests an unbounded PBKDF2 iteration count.
- CVE-2026-91403, CVE-2026-113470: Updated the Java base image for the backend and database migration containers to Amazon Corretto 17.0.21, which blocks the compromised eMudhra intermediate certificates and removes the affected emSign roots.