Relativity Server release notes

• Product Version: This is the 'base' version of Relativity Server, for example Server 2024 or Server 2023. Remember that Hot Fixes and Patches apply only to specific versions of Relativity Server.
• Update Type: this is the type of installer that the release item was first released in. Some items are first released in Hot Fixes, while others are first released in Patches.
  • Base: these items are included in the initial release for that version of Relativity Server.
  • Hot fix: these items were first released in a Hot Fix (but may subsequently be included in a Patch; if there is a value in the Patch version column, it means that this item is also available in that Patch)
  • Patch: these items were first released in a Patch.
• Hot Fix Version: If the item was first released as a Hot Fix, this column shows the Hot Fix version that the item was first released in. Note that Hot Fixes are cumulative, see Learn more about hot fixes and patches.
  • If Hot Fix version is blank, that particular item was not first released as a separate Hot Fox, but was included in the Base release or in a Patch.
• Patch Version: This is the Patch version that the release item is included in. Patches are essentially collections of all preceding Hot Fixes for that version of Relativity Server, but can include additional fixes as well.
  • If Patch version is blank, that item was either included in the initial base release, or is only available as a Hot Fix and is not yet included in a Patch.
• Initial Release Date: This is the date when that item was released for the first time.
• Type: This categories the change type of the item, for example a Resolved Defect or an Enhancement.
• Feature: This is the feature/application within Relativity that the item applies to.
• Description: This is the release item description.
  Tip: you can search the Description field by entering text into the Search box. If you want to determine if the same fix was released for both Server 2024 and Server 2023 for example, use the Search box to filter rows for the specific item you are looking for, which will then tell you which release that item is included in for Server 2024 and in which release that item is included for Server 2023.

• Relativity releases hot fixes and patches to remediate select defects and vulnerabilities found in supported Relativity Server versions. Hot fixes are unscheduled update releases to resolve higher impact defects or vulnerabilities. Patches are scheduled update releases that also include fixes for less severe/lower impact issues
• Hot fixes and patches are associated with a specific version of Relativity Server. In other words, Relativity Server 2025 hot fix #1 is built for Relativity Server 2025 and cannot be applied to Relativity Server 2024.
• Hot fixes and patches are cumulative for a base version of Relativity Server. Each hot fix and patch that Relativity Releases includes all previously-released hot fix and patch content for that base version. In other words, hot fix #2 for Relativity Server 2025 includes hot fix #1 for Relativity Server 2025. Patch #2 for Relativity Server 2025 includes patch #1, as well as any hot fixes released between patch #1 and patch #2.
  • This means you do not need to separately install previous hot fixes; the latest hot fix/patch will always include all preceding hot fixes and patches for that version of Relativity server.
• The first digit represents the patch number, and the second digit represents the hot fix number relative to the patch. This new versioning attribute is referred to as the update version.

Consider the diagram below, which illustrates how the new update versioning scheme for Server 2025 would be applied during sequential hot fix and patch releases. In this diagram:

• Hot fix #2 (update.0.2) also includes hot fix #1 (update.0.1) changes
• Patch #1 (update.1.0) includes hot fix #1 and #2, as well as additional new fixes for the patch. (Since hot fix #2 includes hot fix #1, patch #1 includes hot fix #1 as well.)
• Hot fix #3 (update.1.1) includes everything in patch #1. (Therefore, hot fix #3 includes hot fixes #1 and #2, as well as the additional fixes included in patch #1.)
• Hot fix #4 (update.1.2) includes everything in hot fix #3. (And since hot fix #3 includes patch #1, everything up to an including hot fix #3 is included in hot fix #4.)
• Patch #2 (update 2.0) includes patch #1 (update 1.0), hot fixes #3 and #4 (updates 1.1 and 1.2), and additional new fixes for the patch.

Why we publish known issues
Relativity publishes known issues to provide transparency and to give you the information you need when making upgrade decisions. Relativity Customer Support and Engineering publishes known issues at its own discretion based criteria such as on the number of customer reports, the severity of the issue, and the availability of a workaround. Not all defects are published as known issues.

When we publish known issues
The known issues list receives updates when the following occurs:

• Engineering or Support identifies new known issues.
• A monthly update introduces a new known issue.
• A monthly update resolves an existing known issue.

If you're experiencing an issue in Relativity and you don't see it listed on the known issues page, contact Client Services.

Known issues details
The Known Issues page contains the following information about each known issue. You can also sort on each column by clicking the column header:

• Date added - lists the date that the known issue was added to this web page.
• Defect number - lists the defect number. This number is helpful in conversations with Client Services or Sales if you think you're experiencing the Known Issue in your environment.
• Feature - lists the feature of Relativity affected by the Known Issue, so you can identify the Known Issue within a workspace.
• Description - provides an overview of the Known Issue.
• Versions affected - lists the versions of Relativity where the Known Issue appears.
• Version resolved in - lists the versions of Relativity where the Known Issue is resolved so you can make decisions on upgrades. If this column is blank, the known issue is still open.