4 actions required18 new3 security fixes
26.9.0 is our first LTS release under the new versioning. It includes every change since 25.49, the most widely deployed version under the previous versioning. If you are upgrading from 25.49, start with Action required.
Action required 4
-
Migrate your Composer configuration before upgrading. This release changes how organization configuration is structured. Configuration files and secrets must be migrated manually before you upgrade.
-
Organization operators sign in differently. Organization operators now sign in with their username and organization name. Signing in with an email address alone is reserved for root operators. Organization names are no longer case-sensitive.
-
Update CLI scripts that use
--version. The CLI replaces the--versionflag with thecubbit versioncommand. -
Review the new configuration settings before you upgrade:
ENABLE_SAML_SSO(off by default): turns on SAML 2.0 single sign-on (early access).TOGGLE_LEGACY_ORGANIZATION_RESOURCE_ACCESS_ENABLED: turns on organization-level permissions for tenants, swarms, projects, providers and redundancy classes.NEXT_PUBLIC_FT_ENABLE_VIRTUAL_LOCATION,NEXT_PUBLIC_OPERATOR_DASHBOARD_URL,NEXT_PUBLIC_SWARM_MIGRATION_GUIDE_URL: Composer console settings.- The new gateway, Offloader topology and cache settings.
Composer Dashboard 8
-
New
New DS3 Composer experience, now generally available: new sign-in and sign-up, an onboarding wizard, an infrastructure dashboard, management of swarms, gateways, tenants and locations, IAM user management and a self-service profile.
-
New
Infrastructure management:
- View, update and delete locations.
- Create and manage swarms.
- Deploy gateways automatically.
- Create tenants, with verification of domain and gateway ownership.
- Manage tenant connections.
-
New
Legacy swarm migration to Kubernetes: import your agent-to-infrastructure mapping (upload or paste it), review the imported agents, then migrate one nexus at a time while following the progress of each agent. Each nexus has planned downtime during its migration. Migrated gateways can be attached to existing tenant connections.Also: Coordinator
-
New
Two-factor authentication in Composer, the CLI and the IAM API, with recovery codes. Sensitive actions ask for a code, and changing your two-factor settings signs out your other sessions.Also: Coordinator, CLI
-
Improved
Clearer emails: activation emails say when the link or command expires, a new email confirms password changes, and organization and tenant names are shown correctly.Also: Coordinator
-
Fixed
"Open console" links go to the correct gateway and domain, and the DNS "All set" status is shown consistently.
-
Fixed
Layout issues on small screens are fixed.Also: S3 Console
-
Security
Console analytics no longer collect sensitive information.Also: S3 Console
S3 Console 8
-
New
Early access SAML 2.0 single sign-on for IAM and the S3 console login page, including IdP-initiated sign-in. Turn it on with
ENABLE_SAML_SSO.Also: Coordinator -
New
Bucket policies in the S3 console, with a policy generator, CRN v2 support and guidance on when to use IAM policies versus bucket policies.Also: S3
-
New
Delete and restore buckets (soft delete).Also: S3
-
Improved
Clearer object lock behavior: the console explains that object lock can only be enabled when a bucket is created.
-
Fixed
The S3 console no longer crashes when a bucket is deleted or a download fails, and it starts up reliably.
-
Fixed
Bucket lists and bucket policies retry automatically after temporary server errors.
-
Fixed
The object lock settings page shows an error instead of loading indefinitely.
-
Fixed
Layout issues on small screens are fixed.Also: Composer Dashboard
-
Security
The S3 console no longer keeps S3 access keys after the browser tab is closed. You will need to enter your keys again in each new session.
-
Security
Console analytics no longer collect sensitive information.Also: Composer Dashboard
S3 7
-
New
List pending multipart uploads.
-
New
Ranged downloads through the Offloader.
-
New
Lifecycle rules for noncurrent versions on buckets where versioning is suspended, and APIs to migrate versioned buckets and object versions.
-
New
Bucket policies in the S3 console, with a policy generator, CRN v2 support and guidance on when to use IAM policies versus bucket policies.Also: S3 Console
-
New
Delete and restore buckets (soft delete).Also: S3 Console
-
Improved
Faster responses: gateway, tenant and availability lookups are now cached.Also: Coordinator
-
Improved
Clearer API errors: every S3 error response, including rate-limit responses, carries an error-code header.
-
Improved
Stricter request validation: requests that aren't valid UTF-8 are rejected, and bucket names that aren't valid UTF-8 are no longer listed.
-
Fixed
The pending multipart uploads list paginates correctly.
Coordinator 16
-
New
Smart Data Placement for gateways created with the new flow, including the storage classes each gateway allows.
-
New
Email verification with a public confirmation page.
-
New
Audit log of authentication events: sign-ins, sign-outs, failed sign-in attempts, password changes and two-factor checks.
-
New
Organization-level permissions across tenants, swarms, projects, providers and redundancy classes. Invited operators automatically get read-only access to the organization.
-
New
Tenant v5, Swarm v5 and Gateway v5 APIs, all available in the SDK. The SDK also covers tenant connections, location management, legacy swarm migration, email verification and two-factor authentication.
-
New
CubQL supports the
notinoperator. -
New
Infrastructure management:
- View, update and delete locations.
- Create and manage swarms.
- Deploy gateways automatically.
- Create tenants, with verification of domain and gateway ownership.
- Manage tenant connections.
-
New
Legacy swarm migration to Kubernetes: import your agent-to-infrastructure mapping (upload or paste it), review the imported agents, then migrate one nexus at a time while following the progress of each agent. Each nexus has planned downtime during its migration. Migrated gateways can be attached to existing tenant connections.Also: Composer Dashboard
-
New
Early access SAML 2.0 single sign-on for IAM and the S3 console login page, including IdP-initiated sign-in. Turn it on with
ENABLE_SAML_SSO.Also: S3 Console -
New
Two-factor authentication in Composer, the CLI and the IAM API, with recovery codes. Sensitive actions ask for a code, and changing your two-factor settings signs out your other sessions.Also: Composer Dashboard, CLI
-
Improved
Recovery is more robust:
- A ring can recover from several broken nexuses.
- A retried recovery continues where it stopped.
- A recovery that cannot complete fails with a clear reason.
- Running the same recovery again is safe.
- Recovery emails show the progress of each nexus and link to the dashboard.
-
Improved
Agents behind NAT or with dynamic IP addresses announce their real address to peers, so swarms stay reachable.
-
Improved
Swarm-level labels in Prometheus metrics.
-
Improved
Smoother rolling restarts: services finish in-flight work before shutting down.
-
Improved
API keys are hidden after creation: the CLI and SDK show the full secret only once, when the key is created.Also: CLI
-
Improved
Faster responses: gateway, tenant and availability lookups are now cached.Also: S3
-
Improved
Clearer emails: activation emails say when the link or command expires, a new email confirms password changes, and organization and tenant names are shown correctly.Also: Composer Dashboard
-
Fixed
Duplicate
tenant.createdwebhooks are no longer sent. -
Fixed
Quotas match between DS3 and Resource Monitor, use UTC periods consistently, and send notifications at the right thresholds.
-
Fixed
Accounts scheduled for deletion stay recoverable for the whole grace period.
-
Fixed
You can no longer create two organizations whose names differ only in capitalization.
-
Deprecated
Legacy Offloader routes are deprecated and will be removed in a future LTS release. Please migrate to Gophloader. We will confirm the removal version at least two LTS releases (six months) in advance.
CLI 3
-
New
New CLI commands for:
- locations, swarms, gateways, domains, tenants and tenant connections
- IAM users, including password reset and API keys
- two-factor authentication:
iam user tfa enable|disable, andauth login --tfa-codefor non-interactive sign-in
-
New
CLI configuration v2: separate endpoints for each profile, and an
--endpointsflag onauth login,auth signupandauth activate. The CLI also has new output modes and clearer table, tree and text output. -
New
Two-factor authentication in Composer, the CLI and the IAM API, with recovery codes. Sensitive actions ask for a code, and changing your two-factor settings signs out your other sessions.Also: Composer Dashboard, Coordinator
-
Improved
API keys are hidden after creation: the CLI and SDK show the full secret only once, when the key is created.Also: Coordinator
-
Deprecated
The
--versionCLI flag has been removed. Usecubbit versioninstead.
General 1
-
Security
Sign-in, project invitations, account creation and email templates have been hardened. We recommend that everyone running 25.49 upgrade.