Release Notes

Download this version
Public

11.0.16.9453: May 29 2025

New

All platforms - Server: Support for custom client messages in OnPremise servers

Administrators of OnPremise servers now have the ability to force-display custom messages directly on the client side. Whether you're issuing a critical security alert, rolling out new usage policies, or just want to keep users informed about important updates, this feature puts communication front and center.

== How do I use it? ==

This new functionality is available under the WebAdmin section "Advanced -> Global security settings -> Custom client message", and supports a basic subset of HTML tags.

E.g.

<p style='background-color:#FFCCCB; padding:8px; margin:0; font-size:12px;'>
    <b>CONFIDENTIAL INFORMATION NOTICE</b> - 
    You are accessing protected content. <b>DO NOT</b> share, copy, or distribute without proper authorization.
</p>

Once set, clients connecting to any workspace under the server will display a banner with the configured notice.

ScreenshotScreenshot

== Who can remove the banner? ==

Only administrators can remove it by reseting the "Custom client message" field in the WebAdmin.

== A note on visibility ==

This feature is currently supported by the Unity Version Control desktop client, and will be extended to Gluon in a future release.

Bug

All Platforms - Desktop GUI: Fixed opening plastic links for migrated @unity organizations

Previously, plastic links for code reviews or diff would fail to open with the Desktop GUI for newly migrated @unity organization having names in CamelCase. With this fix, it is now possible to open these links.

Bug

All Platforms - Desktop GUI: Fixed broken onboarding in DVCS edition

The user account sign-in did not work as expected in the Home view for the DVCS edition version. It was because the account was managed as a cloud account instead of an on-premises account.

Now the user can sign in to the local server and obtain the list of repositories for this server.

Bug

All Platforms - Server: Merge rules now correctly enforced when using old repository names

Previously, if a client attempted a merge using the repository name that existed before a rename, the server would bypass merge rule validation. This issue has been resolved - merge rules are now correctly applied even when the client refers to the repository by its old name.