Unity Version Control 11.0.16.9453

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

All platforms - Server: 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.

All platforms - Server: == How do I use it? ==

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

All platforms - Server: E.g.

All platforms - Server: Once set, clients connecting to any workspace under the server will display a banner with the configured notice.

All platforms - Server: == Who can remove the banner? ==

All platforms - Server: Only administrators can remove it by reseting the "Custom client message" field in the WebAdmin.

All platforms - Server: == A note on visibility ==

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

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

All Platforms - Desktop GUI: 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.

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

All Platforms - Desktop GUI: 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.

All Platforms - Desktop GUI: Now the user can sign in to the local server and obtain the list of repositories for this server.

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

All Platforms - Server: 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.