Skip to main content
October 20, 2026 Domino 6.3.1 is a patch release for Domino 6.3 with security updates and bug fixes. It adds in-app notifications for Governance, lets administrators choose whether to install Domino Model Monitor (DMM), and fixes upgrade failures from 6.3.0. Additional component updates are available in ddlctl and fleetcommand-agent release notes.

​
Governance

​
In-app notifications for approvals, findings, and stage assignments

Governance now sends in-app notifications, in addition to email, when an Approval is requested, a Finding is assigned or reviewed, or a bundle stage is assigned to you. See Review bundles.

​
Notes for platform administrators

  • DMM is installed only when dmm.enabled is true. See dmm.enabled.
  • Deployments without model serving can archive Projects. On those deployments, set the com.cerebro.domino.modelServing.disabled configuration record to true; see Configuration records.
  • Admin Toolkit checks are broader. The Admin Toolkit checks more conditions, runs node checks on every node, and uses updated thresholds, so it can report warnings after the upgrade that it didn’t report on 6.3.0.

​
Bug fixes

  • Runs no longer fail intermittently while Preparing.
  • Service account tokens no longer expire after about 8 hours. Replace any token you created on 6.3.0.
  • Environment builds no longer fail when an unrelated container registry is unreachable or has invalid credentials.
  • Apps no longer return “URL Not Found” on clusters whose ingress controller requires an ingress class. Restart affected Apps after you upgrade.
  • Connecting to a Workspace through Domino Connect no longer removes Organization memberships that come from single sign-on (SSO).
  • Domino CLI sign-in no longer fails with an authentication error.
  • After an administrator changes a user’s password, the confirmation page shows the correct title.
  • The admin NetApp Volumes page lists all volumes instead of only the first 50.
  • Failed NetApp Volume creates and deletes report an error instead of leaving the volume out of sync with NetApp storage.
  • Add to Bundle works for a Job’s result files.
  • Gates from inactive policy versions no longer apply to a bundle.
  • A Project’s Overview no longer shows an error for a Git repository with no commits or no files.
  • Executions on Data Planes no longer get stuck in Pending.
  • Upgrades from 6.3.0 no longer fail when Dataset permissions contain duplicates. If Support applied a temporary fix for this issue, contact Support before you upgrade.
  • Upgrades after a backup and restore no longer stop during a permissions migration. If an upgrade already stopped this way, contact Support.
  • Restoring a backup into an empty PostgreSQL instance no longer fails.
  • Deployments with network policies turned off now create the databases for tags, Properties, and NetApp Volumes. Upgrading to 6.3.1 creates any that are missing.

​
Known issues

The Domino 6.3.0 known issues also apply to 6.3.1.

​
Validated frameworks

Domino 6.3.1 ships the same Apache Spark, Dask, and Ray versions as 6.3.0; see Validated frameworks.

​
Upgrade notes

If you upgrade from Domino 6.2.x, the Domino 6.3.0 upgrade notes also apply.
Keep dmm.enabled: true on deployments that use DMM, including when you migrate to a new installation. Otherwise, the upgrade or migration removes DMM or skips its data.
  • Users can’t sign in for a few minutes during the upgrade. Keycloak restarts during the first upgrade to 6.3.1, so plan the upgrade for a maintenance window.
Kubernetes support is unchanged from 6.3.0; see the Kubernetes compatibility matrix.

​
Breaking changes & deprecations

  • git-lfs is removed from Domino environment images. If your workloads use Git Large File Storage (LFS), add git-lfs to your environment’s Dockerfile instructions; see Customize your Environment.
  • The remaining Project status and Jira elements are removed from the UI. This completes the removal that started in 6.3.0: status tabs, columns, badges, and filters are gone from the Projects list, the Projects Portfolio, Home, and the Activity feed. Project status is still available through the API.
Last modified on October 20, 2026