Unity Version Control 11.0.16.10330

All platforms - Desktop GUI : Markdown support in attribute values: Markdown support in attributes:

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:

All platforms - Desktop GUI : Markdown support in attribute values: Admins can seed a Markdown skeleton in the attribute's comment field so anyone applying it lands in the editor with the template preloaded.

All platforms - Desktop GUI : Markdown support in attribute values: Example:

All platforms - Desktop GUI : Markdown support in attribute values: Values now go up to 5,000 characters (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.

All platforms - Desktop GUI : confirm before deleting an attribute from an object: The confirmation dialog shows a preview: a one-line snapshot of the value being deleted so you can double-check it's the correct one. It offers two options:

All platforms - Desktop GUI : confirm before deleting an attribute from an object: This change applies to every attribute-value deletion in the Desktop GUI. There's nothing to configure.

All platforms - Command-Line: cm attribute set now accepts a file parameter for the attribute value: `cm attribute set` now has a `--valuecontents=` option that sets an attribute value from a file instead of a command-line argument. Use this for multi-line values or values containing special characters such as URLs with `?` or `&` .

All platforms - Command-Line: cm attribute set now accepts a file parameter for the attribute value: Example:

Plain text: keeps the compact single-line dropdown.

Markdown (existing value, pasted value, or default template): flips into a side-by-side raw editor and live preview that updates as you type.

Yes: removes the attribute value from the object.

No / close: makes no changes.

Cloud Server : Updating an existing trunkbot could break the mergebot: Previously, updating a trunkbot from the dashboard without including the internal field `bot_user` would delete the missing field on the server side.

Cloud Server : Updating an existing trunkbot could break the mergebot: The mergebot then failed to start. The server log showed "The mergebot cannot be started since its user ApiKey [] doesn't exist".

Cloud Server : Updating an existing trunkbot could break the mergebot: Now, if the field is missing from the update request, the server now preserves its from the existing configuration.

All platforms - Command-Line: cm attribute set can't 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 show the command usage.

All platforms - Command-Line: cm attribute set can't set values with wildcards: Example of a command that previously failed and now works: