Domino 6.3.0

​

New features

​

Extensions

​

Coding assistants in Workspaces

​

HPC workload support with Slurm

​

Enhancements

• Full App SDLC. Take Apps from private draft to an immutable published App version with distinct create, publish, and deploy stages. Pinned commits make versions reproducible, restartable, and easier to roll back; see the App lifecycle and App versioning and reproducibility.

• Runtime configuration for flow runs. Rerun a registered Flow with different inputs, Compute Environments, Hardware Tiers, or Git references without editing its definition. Apply the same overrides from the UI, API, or CLI; see Launch Flows.

• Consistent paths and secondary repositories in Flow tasks. Use the same input and output paths across Flows, Workspaces, and Jobs. Flow tasks can also pin a branch, tag, or commit from an imported Git repository; see Define Flows.

• Governance enforcement for Apps and agents. Turn governance requirements into deployment gates for Apps and agents by linking them to governance bundles. Required policies can block deployment, while App versions carry Evidence forward with version diffs; see Govern models, Apps, agents, and files.

• Knowledge management with tags and properties. Give teams a shared way to organize and discover Domino assets. SysAdmins and Librarians can define tags and typed Properties, while users can find classified assets through search, filters, and the Tag Browser; see Knowledge management.

• Governance bundle lifecycle and review controls. See compliance status at a glance and move completed bundles to Completed or Archived. Reviewers can reset sequential bundles, replace their primary policy, and select eligible Project collaborators as approvers; see Work with bundles.

• Governance stage notifications and reassignment. Keep reviews moving with email and in-product notifications when stages start. A global Stages view shows status and assignees and supports bulk reassignment; see Manage stages across bundles.

• Flow artifacts as governance attachments. Capture Flow outputs directly in governance bundles. Flows can attach files automatically, or users can attach them from a run’s Artifacts tab; see Flow artifact files.

• Periodic revalidation for Governance. Keep Approvals current with a recurring, organization-wide renewal schedule. Bundles remain compliant during the renewal window and become non-compliant if approval expires; see Periodic revalidation.

• Policy versioning for Governance. Develop changes to a published policy in a draft, then choose whether the update is mandatory and whether existing Approvals remain valid. Compare versions from the Changes tab; see Create a new version of a policy.

• Personal Access Tokens replace user API keys. Move user-context API access to expiring personal access tokens (PATs) that administrators can audit and revoke. Starting in 6.3, PATs are the supported replacement for legacy user API keys, which remain functional but are deprecated; see Personal access tokens.

• Cluster-specific API documentation. Explore cluster-specific API documentation directly at https://<your-domino-domain>/docs. See the API browser for details.

​

Notes for platform administrators

• Slurm support is enabled when a Data Plane is deployed. Set compute_clusters.slurm.enabled to true when deploying the Data Plane; adding Slurm later requires a redeployment. Create the required Compute Environments, worker Hardware Tiers, and shared Dataset, and enable Data Plane storage and Workspaces for remote Data Planes; deployments that leave Slurm disabled require no action. See Administer Slurm.

• HPC Job submission from the UI and API is off by default. Set ShortLived.EnableHPCJobs to true to add a Run button to the HPC tab. Terminal submission needs no flag; see Administer Slurm.

• Configuration records have Basic and Advanced views. Basic provides validated controls for common settings, while Advanced retains the full editor. The new interface is off by default; set EnableNewCentralConfigsEditor to true to enable it without changing existing values, or leave it off with no action required. See Basic and Advanced views.

• Administrators can start another user’s stopped Workspace through the API. The adminStartWorkspace operation requires ManageWorkspaces and preserves the Workspace owner’s previous mounts. Pair it with the existing stop operation to automate restarts; see Start a user’s Workspace as an administrator.

• The platform Grafana instance is operator-managed. Manage custom dashboards, alerts, contact points, and notification policies at /grafana as Kubernetes resources. Don’t edit Domino-managed resources because upgrades overwrite them; deployments without custom Grafana content require no action. See Manage Grafana dashboards and alerts as custom resources.

• Legacy Grafana remains available during the 6.3.x migration window. Migrate custom content from /grafana-classic to /grafana before upgrading beyond 6.3.x; see Access the legacy Grafana instance during migration and the Support site knowledge base (requires sign-in).

• Deployment identification for product analytics. Set the optional customer_name and deployment_name values to identify your organization and environment in product analytics and Support cases. Changes take effect after Domino services restart; see Deployment identification.

​

Bug fixes

​

Known issues

​

Validated frameworks

​

Upgrade notes

​

Breaking changes & deprecations

• Legacy Domino user API keys are deprecated. Existing keys still work in 6.3, but migrate existing integrations and build new ones with a Personal Access Token or Domino Service Account; see Domino API authentication.

• The project.tag.approved= search operator is removed. Filter by tag from the search bar or filter panel instead; project.tag= is unchanged. See Use Domino search.

• Project Tasks, Goals, and the Project Stages and Status UI are removed. Use your organization’s issue tracker for task-level milestones; the read-only Project Status badge, Activity feed, and backend Goal APIs remain available. Domino migrates existing Project goal comments to bundle comments during the upgrade.

• The Project-level Jira integration UI is removed. Project-to-ticket links and task synchronization are no longer shown, while the backend Jira APIs and deployment-wide OAuth registration remain unchanged.

• The legacy platform Grafana instance at /grafana-classic is deprecated. Migrate custom content to /grafana before upgrading beyond 6.3.x; see Access Grafana and the Support site knowledge base (requires sign-in).