Skip to content

Release Notes - Version 2.3.0

Release Date: August 20, 2026

🎉 Highlights

Version 2.3.0 introduces a full admin audit logging capability — administrators can now review a complete trail of platform configuration actions directly from the UI or the API. Team management is enhanced with enable/disable controls and an improved user blocking policy for billing-account owners. Queue scheduling gains better support for customer-use queues in preemptible and dedicated mode, with a new toggle on the queue status view for quick adjustments. Authentication reliability is strengthened across Okta token-exchange, Bearer, and email-based password-reset flows. The release also removes legacy per-workload limit tracking in favor of consistent per-user queue limits throughout the platform.

🚀 New features

🗒️ Admin audit logging

Administrators and superusers can now browse a read-only audit trail that records who performed each administrative action, when it occurred, and what was changed. The log is available as a read-only viewer in the UI for superusers and is captured at the API level for all administrator operations. The sidenav entry for Audit Logs is conditionally hidden when the audit feature flag is disabled, keeping the navigation clean for environments where the feature is not yet active. Audit log error messages include accessibility attributes and i18n copy so screen readers and keyboard navigation work correctly with the view.

🏳️ Team enable/disable

Administrators can now enable or disable teams using a new toggle in both the admin API and the admin UI. Disabled teams remain in the system but their access is suspended, giving operators finer control over team lifecycle without requiring deletion and recreation. User deletion is also blocked when the user is the billing-account owner of one or more teams, preventing orphaned billing relationships.

🔀 Customer-use queue allocation and toggle

Queues marked as is_customer_use can now be correctly allocated when configured in preemptible or dedicated mode — a previous restriction that prevented these queues from being scheduled has been removed. A new customer-use toggle is visible on the queue status view below the existing enable/disable control, allowing administrators to change the allocation mode without leaving the status panel.

🔧 Improvements

  • Okta authentication hardening — User lookup now falls back to the preferred_username and email claims, and last_login is reliably updated on both token-exchange and Bearer authentication paths.
  • Password reset loop prevention — Password age is now refreshed after an email-based password reset, preventing users from being immediately prompted to reset again.
  • Per-user queue limit enforcement — Legacy per-workload limit tracking has been removed; all limit enforcement now uses per-user queue limits throughout the API and UI, simplifying the scheduling pipeline and removing deprecated max_accelerators_per_job and max_cores_per_job references.
  • Queue ordering by free capacity — Compatible CI queues are now ordered by their free-capacity cache value, giving the scheduler a more accurate view of available resources for interactive job placement.
  • Web terminal session cleanup — Shell sessions are now explicitly terminated when a browser closes a web-terminal connection, preventing orphaned processes on the host.
  • Teams filter by enabled status — A new enabled query parameter on the teams/ endpoint makes it easy to manage active and inactive teams from both the API and admin views.
  • Responsive billing tables — The billing and transaction Material tables are now wrapped in a horizontal scroll container, preventing content from being clipped on narrower viewports.
  • Application wizard DTO migration continued — The application create and edit wizards were migrated to strongly typed WriteAppRequest and PatchWriteAppRequest DTOs, reducing reliance on ad-hoc form mutation and continuing the migration effort started in previous releases.

🐛 Bug fixes

  • Fixed application wizard Settings form labels not visible after entering a value — labels are now correctly displayed once a field is populated
  • Fixed duplicate settings keys being allowed in the application wizard Settings form — a guard now prevents submitting duplicate entries
  • Fixed S3 dataset cleanup being skipped when a satellite omits the workload label from its job completion signal
  • Fixed to_accepted state transition not being permitted from EXPIRED — resolves a sign-up crash when an expired invitation is redeemed
  • Fixed field-level validation not returning a clear error for duplicate team names — a descriptive error is now returned instead of a generic response
  • Fixed free-capacity cache Celery deduplication not handling scenarios where the cache worker is temporarily unavailable
  • Fixed missing invitation names for users completing sign-up through Okta — name fields are now back-filled from the invitation record
  • Fixed double-quoting of the Redis hostname variable in deployment workflows
  • Fixed npm high-severity vulnerabilities in Angular and Babel production dependencies

🔒 Security

  • nginx 1.30 — nginx was upgraded to remediate CVE-2026-60005
  • SSL certificate renewal — SSL certificate paths for aac-api.amd.com and the staging environment were updated to the 2026–2027 certificate cycle

🧹 Cleanup

  • Removed the AcceleratorProcessingUnit model and its database table — the APU concept has been retired from the platform
  • Removed unused ConfigSettings model fields and their corresponding theme fields from the config API response
  • Removed dead email templates; the emails management command was extended to cover active templates
  • Removed deprecated minimum-cores filter from the queue list filter panel in the UI
  • Removed dead WizardJob helper methods and unused queue wizard mode state
  • User account deletion in the UI now calls the archive endpoint instead of the legacy delete endpoint

← Back to What's New | Previous Release (v2.2.0) →