Heads up before we dive in: we know the release notes for this build are currently not showing up in the Desktop GUI’s update window or on the Unity dashboard. A few of you already flagged it over in this forum — thank you, and sorry for the confusion. We’re actively working on a fix. In the meantime, we’re publishing the notes here so nobody has to update blind. Appreciate your patience!
This build focuses on making attributes a lot more useful — Markdown everywhere they matter, safer deletes, and CLI ergonomics for the awkward cases (multi-line values, URLs with ? and &). Plus a Cloud Server fix that quietly rescues trunkbots from a very frustrating failure mode.
All platforms — Desktop GUI: Markdown support in attribute values
Attribute values now carry Markdown. The Apply Attribute dialog picks the layout based on the content:
- Plain text: keeps the compact single-line dropdown.
- Markdown (existing value, pasted value, or default template): displays a side-by-side raw editor and live preview that updates as you type.
Admins can seed a Markdown skeleton in the attribute’s comment field so anyone applying it has the template preloaded in their editor. Wrapping the template in quotes is optional:
default: # What changed
## Motivation
## How to test
-
-
Attribute values can now contain 5,000 characters (previously, the limit was 1,000).
All platforms — Desktop GUI: confirm before deleting an attribute from an object
The X button on an attribute pill in the object details panel used to delete the value silently. Now the button asks for confirmation before deleting.
The confirmation dialog shows a preview — a one-line snapshot of the value being deleted so you can double-check it’s the right one. Then, the options:
- Yes: removes the attribute value from the object.
- No / close: make no changes.
Nothing to configure. This applies to every attribute-value deletion in the Desktop GUI.
All platforms — Command-Line: cm attribute set now accepts a file parameter for the attribute value
Added --valuecontents= to cm attribute set so you can set an attribute value from a file instead of the command-line argument. Handy for multi-line values or values with special characters like URLs containing ? or &.
Example:
$> cm attribute set att:Status br:/main --valuecontents=AttributeValue.txt
Bug: Cloud Server: Updating an existing trunkbot could break the mergebot
Previously, updating a trunkbot from the dashboard caused an internal field not included in the request to be lost.
The mergebot then failed to start with The mergebot cannot be started since its user ApiKey doesn’t exist in the server log.
Now, if the bot_user field is missing from the update request, the server keeps its existing value in the config.
Bug: All platforms — Command-Line: cm attribute set cannot set values with wildcards
Fixed an issue where attribute values containing ? or * characters were incorrectly treated as file wildcards, causing the command to fail and print the command usage.
Example of a faulty command that now works fine:
$> cm attribute set att:url br:/main "https//myservice.com/api/list?querymode=default"
That’s the full changelog for 11.0.16.10330. Thanks again to everyone who reported the missing release-notes issue — we’re on it, and we’ll get the in-GUI and dashboard listings back to normal as soon as possible. See you in the next one!
Installers link here: https://docs.unity.com/en-us/unity-version-control/installation-landing and here: Plastic SCM - Download Plastic SCM
