Unity Version Control 11.0.16.10350
19 documented changes.
- Version
- 11.0.16.10350
- Product
- Unity Version Control
Unity Version Control 11.0.16.10350
New
- Change
All platforms - Desktop GUI: Show attributes in Code Review window: The Code Review window now displays the attributes of a branch or changeset next to the Conversation panel. Reviewers can read attribute values without switching to the Branch Explorer.
- Removal
All platforms - Desktop GUI: Show attributes in Code Review window: The attributes are shown with the same components used in the Branch Explorer, so they can be added, edited, and removed from the panel in the same way.
- Change
All platforms - Desktop GUI: Show attributes in Code Review window: Screenshot of a Code Review window including the new attributes panel:
Bug
- Change
All platforms - CLI : cm changelist add no longer deletes the target changelist when adding a file that was checked out and changed: Rebuilding a chagelist after adding a checked-out and changed file reset the changelists's contents. This was because files carrying the `CheckedOut` change type had two IDs: One for the entry key and one for all other uses.
- Change
All platforms - Command-line : cm status --xml reports the combined CO+RP and CO+CP status codes: When applying a shelve to a workspace, an item can be checked out and replaced, or checked out and copied as a new file.
- Change
All platforms - Command-line : cm status --xml reports the combined CO+RP and CO+CP status codes: `cm status --machinereadable` already reported these as `CO+RP` and `CO+CP` , but `cm status --xml` reported only `CO` , so a tool parsing the XML can't tell a replaced revision from a copied one.
- Change
All platforms - Command-line : cm status --xml reports the combined CO+RP and CO+CP status codes: The `Type` field in the XML output now carries the combined code and matches the machine-readable output. The `--short` and `--compact` text output report the same codes.
- Change
All platforms - Command-line : cm status --xml reports the combined CO+RP and CO+CP status codes: The `Type` field distinguishes these states:
- Change
All platforms - Command-line : cm status --xml reports the combined CO+RP and CO+CP status codes: A replaced or copied item that is not checked out still reports `RP` or `CP` .
- Change
All platforms - Desktop GUI : Render Markdown in attribute tooltip: When the Attributes panel trims an attribute with an ellipsis, hovering shows a tooltip with the full content.
- Change
All platforms - Desktop GUI : Render Markdown in attribute tooltip: Previously, Markdown-formatted attributes displayed as raw text in that tooltip. The tooltip now renders Markdown using the same preview as the edit-attribute dialog: headings, lists, links, and images all display formatted. Long values scroll inside the popup, links are clickable, and moving the cursor into the popup keeps it open.
- Change
All platforms - Desktop GUI : Render Markdown in attribute tooltip: An attribute with the tooltip showing Markdown content:
- Change
All platforms - Desktop GUI - CLI : Xlink conflict dialog resolves the target changeset ID instead of showing the raw GUID: When merging two branches that both changed a read-only Xlink, the Xlink conflict view used to show each side's target as a raw changeset GUID. The Keep-source and Keep-destination buttons carried the same GUID. This made it hard to know which changeset each side pointed to.
- Change
All platforms - Desktop GUI - CLI : Xlink conflict dialog resolves the target changeset ID instead of showing the raw GUID: The dialog now resolves the GUID to the changeset ID when the target is reachable. If the target changeset was purged or the target repo can't be reached, the dialog still shows the raw GUID.
- Fix
Cloud Server: Editing a running mergebot duplicated it: Previously, editing a running cloud mergebot from the dashboard registered a duplicate in-memory instance each time it was saved. Every duplicate reacted independently to the same branch-resolved event, so each resolve triggered multiple merge attempts: one real merge and the rest reporting `MergeNotNeeded` .
- Change
Cloud Server: Editing a running mergebot duplicated it: Now, the start/stop lifecycle is handled in a single place, so editing a running mergebot results in exactly one stop and one restart.
All platforms - Command-line : cm status --xml reports the combined CO+RP and CO+CP status codes
- Change
`CO+RP` : The item is checked out and its revision was replaced, for example after applying a shelve.
- Change
`CO+CP` : The item is checked out and is a copy. That is, it's a new file.
- Change
`CO+CH` : The item is checked out with local changes. This code already worked and is listed here for contrast.