Release Notes

All platforms - Desktop GUI: Diff panel in Branch Explorer and Query view details

The Branch Explorer and Query views now display a diff tree below the properties in the Details panel when selecting a branch, changeset, or label. For branches, you can switch between viewing the entire branch diff or the changeset-by-changeset diff.

Also, now the Details panel width in the Branch Explorer is preserved between sessions.

Screenshot

All platforms - Desktop GUI: Embedded diff viewer in the Branch Explorer

The Branch Explorer can now show file diffs inline, in a new panel that appears below the diagram. Double-click a file in the Details diff tree, or pick "Diff" from its context menu, to open the embedded viewer; click its Close button to hide it.

The diff tree context menu also gains a new "Diff in a separate window" entry, which opens the standalone diff window as before.

Screenshot

All platforms - Desktop GUI: Show repository tree for selected labels

The Labels view details panel and the Branch Explorer details panel now show the repository tree at the labeled changeset when a label is selected, providing a meaningful snapshot of the tree at that point in history. Previously, both views showed the diff of the labeled changeset, which is not useful for a single label. Selecting a changeset or branch in the Branch Explorer still shows the diff as before.

Right-click actions on items in the tree (Open, Diff with previous, Show history, Save revision as, External tools, filter rules) work the same as in the standalone "Browse repository" view. The label name in the Properties header is no longer clickable in the Labels view details panel.

All platforms - Desktop GUI: Changeset color configuration in Branch Explorer

The changeset color configuration options are added back to the Branch Explorer, now included in the dedicated settings window as a new tab. Changesets can be colored by user and by replication source, and both options can be combined.

User avatars can also be displayed independently from the changeset colors. When avatars and colors are both active, the colors are displayed in the outer ring around the avatar.

Screenshot

All platforms - Desktop GUI: Properties panel shows repository and replication source

The Properties panel in the Details view now displays the repository name next to the object title, and the replication source below the object details when available.

Screenshot

All platforms - Desktop GUI: Added vertical separator between attribute badge action buttons

In the attributes panel, the edit and delete buttons on each attribute badge were placed directly next to each other with no visual separation. A vertical line now divides the two buttons, drawn in the same color as the badge border, along with extra spacing for a cleaner look and better usability.

All platforms - Desktop GUI: Show changeset number in Branch Explorer on hover

When you point at a changeset in the Branch Explorer, its changeset number now appears in a small label above the node, so you can read it at a glance.

Screenshot

This feature is enabled by default for all users from this version. You can turn it off from the Branch Explorer display options.

All platforms - Desktop GUI: Settings button moved to bottom of Branch Explorer

The Settings button in the Branch Explorer was placed at the top of the buttons panel, where the Home button used to be, causing users to accidentally click it. It has been moved to the bottom-left corner of the panel, next to the Zoom Out button.

Screenshot

All platforms - Desktop GUI: Show larger home icon in Branch Explorer when avatars are hidden

In the Branch Explorer changeset shape, the home icon stayed small even when contributor avatars were turned off, so it was hard to see. With avatars disabled, the home icon again fills the changeset shape; with avatars enabled, it stays a small overlay in the corner. The checked-out changeset continues to use the larger home glyph either way.

Screenshot

All platforms - Desktop GUI: Toggle hidden-branch changesets in Changesets view

You can now toggle whether changesets from hidden branches are shown in the Changesets view. By default, hidden-branch changesets stay hidden, and enabling the toggle updates the list immediately so you can inspect those changesets without first unhiding branches.

All platforms - Desktop GUI: Clickable changeset links in the merge xdiff header

The xdiff window opened from "Diff source with destination" during merge conflict resolution now displays clickable changeset links in place of the plain "cs:NNN" labels at the top of each side. Clicking a link opens the changeset DiffWindow with all the changes in that changeset — the same view as the existing changeset link in the History view.

All platforms - Desktop GUI: Details panel remembers open/closed state

The Branch Explorer, Branches, Changesets, Labels, and Attributes views now persist the details panel visibility and width across sessions. Previously, the details panel always reverted to its default state when reopening a view or restarting the application. The panel state is saved automatically when closing the view and restored the next time it loads.

All platforms - Command-line client: New cm admin hashalgorithm subcommand to set the repository hashing algorithm

The cm command-line client now exposes a new admin subcommand that sets the hashing algorithm used by a repository. Only the server administrator can execute it; non-admin callers are rejected with the standard admin-only error.

cm admin hashalgorithm <repspec> (md5 | sha1)

Until now, the per-repository hashing algorithm could only be configured through an in-process server shell command that required raw organization and repository IDs. Operators can now set it through the regular cm CLI using a human-readable repository spec. The new algorithm applies to data hashed by the server from this point on. Changing the algorithm on a repository that already contains data is supported, but operators should consider the implications before doing so.

All platforms - Command-line client: Hash algorithm available as format token

The cm find, cm history, and cm ls commands accept a new {hashalgorithm} output format token that returns the algorithm name (MD5, SHA1) used to produce the revision's {hash} value. The WebAdmin Find JSON endpoint exposes the same field as "hashalgorithm" when explicitly requested. Default output formats are unchanged; the token is opt-in via the --format option (or the fields list, for the JSON endpoint). Revisions without a hash render an empty value.

cm find "revisions where date >= '1 weeks ago'" --format="{hash}|{hashalgorithm}|{owner}|{path}"

All platforms - Command-line client: cm patch supports --clean and --integration options

The cm patch command now accepts --clean and --integration options, which were previously only available in cm diff. This allows generating patches that exclude merge content (--clean) or that show only the changes pending integration into the parent branch (--integration), making it easy to get a focused diff of a task branch for code review or AI-assisted workflows.

All platforms - Server: Unlimited lifespan for Personal Access Tokens

Personal Access Tokens (PATs) can now be configured with an unlimited (never-expiring) lifespan, removing the previous 180-day maximum for CI/CD and automation use cases that require long-lived credentials.

Server-side, the maximum PAT lifespan is controlled by the AccessTokenLifespan setting in server.conf, inside the AccessTokensSettings block. If not explicitly configured, the default maximum lifespan is 180 days.

To enable unlimited PAT lifespans, set AccessTokenLifespan to "infinite":

<AccessTokensSettings>
  <Enabled>true</Enabled>
  <AccessTokenLifespan>infinite</AccessTokenLifespan>
</AccessTokensSettings>

Client-side, the lifetime argument now accepts the "infinite" keyword:

cm accesstoken create "My automation token" infinite

Creating unlimited PATs via the REST API

When creating PATs using the REST APIs, the lifetime field in POST /api/v1/personal-access-tokens is now optional. When omitted, the server's default lifespan applies. To request a token with no expiration, omit the lifetime field and ensure the server is configured with an unlimited lifespan:

POST /api/v1/personal-access-tokens
{
  "description": "My automation token"
}

Windows, macOS — New unified desktop agent: PlasticFS + Cloud Drive

PlasticFS and Cloud Drive are now unified in a single desktop agent: unityvcstray.

This update simplifies startup and background service management.

Backward compatibility is preserved through legacy entry points/wrappers (plasticfs and unityclouddrive) that now route to the unified app.

Additional notes:

* PlasticFS is currently available on Windows only.

* Cloud Drive remains in beta. If you have never used it before, enable it by creating an enableclouddrivetray.token file in your plastic4 config folder.

* This unified tray app will continue to evolve — this is just the beginning, and more capabilities are planned.