Release Notes

All platforms - Desktop GUI: Branch Explorer labels stay visible at lower zoom levels

The Branch Explorer now keeps changeset numbers (on hover), changeset comments, and branch captions visible down to 50% zoom. Below that threshold the three labels hide together, since the text is no longer legible at that scale.

Previously, changeset numbers and comments started hiding below 80% zoom even while still readable, and branch captions remained visible at any zoom level.

All platforms - Desktop GUI: Clickable changeset and branch links in diff and code review panels

The "Diff changeset by changeset" detail panel now shows the full changeset properties panel in both the Branch Diff window and the code review branch view. The changeset number is a clickable link with a right-click context menu (Copy, Copy link, Copy spec, Open), a Copy GUID button, a responsive details layout, and the changeset comment, matching the changeset properties shown in the Branch Explorer. Previously this panel showed a plain text header.

The code review "Review entire branch" and single-changeset views now use the same properties panel, so the branch or changeset name is a clickable link with the same context menu and Copy GUID button. The single-changeset review no longer shows a gray box with a double border.

All platforms - Desktop GUI: Reviewer group members can now mark a code review status

The "Mark Review" button in the code review panel is now enabled for users who belong to a reviewer group assigned to the review, even if they are not explicitly listed as individual reviewers. Previously, the button was only enabled for users directly added to the reviewer list.

When a reviewer group member sets their status, the server adds them to the reviewer list automatically and updates the reviewer group status accordingly.

This behaviour requires an up-to-date server. When connected to an older server, the Desktop GUI will show an error message if users are not already in the reviewer list.

All platforms - Desktop GUI: Automatic handling of .meta files during Add operations

When adding assets to source control in Unity projects, ancestor folders' .meta files are now automatically included in the operation. This prevents orphaned private .meta files when adding nested folder structures.

What changed:

* The existing setting "Rename .meta files automatically" has been renamed to "Handle .meta files automatically" (found in Preferences → Other options).

* When enabled, the Add operation now includes .meta files for all ancestor folders being added to source control.

* The setting continues to control automatic .meta file handling for rename operations as before.

Note: This setting is enabled by default. Disabling it will revert to the previous behavior where only the asset and its ancestor folders are added, without their corresponding .meta files.

macOS - UVCS tray agent: Removed 'System Events.app' permission prompt

Before this version, the macOS UVCS installation in Tahoe would end up with a prompt asking the user to enable this permission in order to start the UVCS tray agent on user login:

 "PlasticSCM.app" wants to control "System Events.app" 

Now this prompt won't arise, and the UVCS tray agent will be enabled on user login through a LaunchAgent plist file deployed in $HOME/Library/LaunchAgents .