21 documented changes.

Version
11.0.16.10694
Product
Unity Version Control
Unity Version Control 11.x release notes

Unity Version Control 11.0.16.10694

Official notes

New

  1. Feature

    All platforms - Command-line: Restore deleted repositories: Added the `cm repository undelete` command. It restores a deleted repository, by name or by GUID, optionally under a new name. Only server administrators can restore repositories, because only they can see deleted ones. `cm repository list` shows deleted repositories as `__DELETED__` . Restoring also requires permission to create repositories on the server.

  2. Change

    All platforms - Command-line: Restore deleted repositories: When several deleted repositories share a name, use the GUID. List the GUIDs with:

  3. Change

    All platforms - Command-line: Restore deleted repositories: On an on-premises server, you can only restore repositories that were deleted while soft delete was enabled. It's disabled by default, so deleting a repository removes it permanently. To enable it, add `deletereposonschedule=true` to the server's `jet.conf` file and restart the server. The server then keeps deleted repositories for 14 days before it removes them. Change the period with `deletereposonschedulegraceperioddays` . Unity Version Control Cloud already has soft delete enabled.

  4. Change

    All platforms - Command-line: Restore deleted repositories: Refer to cm repository undelete.

  5. Feature

    All platforms - Command-line: Comment on a range of lines, a whole file, or any location: Added comments on a range of lines, a whole file, or any other location to `cm codereview comment add` and `cm mergerequest comment add` . Use `--line=-` to comment on a range of lines, counted from 1 and both lines included. `--line` is now optional, so `--path` or `--revision` alone comments on the whole file. Use `--location=:` to store any other location exactly as given, such as a point in an image, for clients that show those locations. `cm find changereviewcomment` prints the first line of a range in its `line` field.

  6. Change

    All platforms - Command-line: Comment on a range of lines, a whole file, or any location: Refer to cm codereview, cm mergerequest, and cm find.

  7. Feature

    All platforms - All clients: Merge requests are now available: Added merge requests. A merge request reviews the changes on a source branch and merges them into a destination branch. Merge requests are available in the desktop application, in the command line, and on the server:

  8. Change

    All platforms - All clients: Merge requests are now available: Use merge requests to review and merge branches, and code reviews to review changesets and shelves. Code reviews for branches are still available.

  9. Change

    All platforms - All clients: Merge requests are now available: Refer to Create and manage merge requests in the desktop application and cm mergerequest.

All platforms - All clients: Merge requests are now available

  1. Change

    In the desktop application, create, review, and merge them. Find them in the Merge Requests tab, and check the merge request of a branch in the Branch Explorer and the Branches view.

  2. Change

    In the command line, use `cm mergerequest` to manage merge requests, and `cm find mergerequest` to list them.

  3. Change

    The server marks a merge request as Merged when you check in a merge from its source branch into its destination branch, even if you ran the merge outside the merge request.

Bug

  1. Fix

    All platforms - Command-line: Adding an existing reviewer no longer duplicates the timeline event: Fixed `cm codereview reviewer add` and `cm mergerequest reviewer add` so they no longer add a "requested review" event to the timeline for users or groups that are already reviewers. A name repeated in the same command is added once.

  2. Change

    All platforms - Command-line: Adding an existing reviewer no longer duplicates the timeline event: Refer to cm codereview and cm mergerequest.

  3. Fix

    All platforms - Command-line: Comments read from standard input no longer keep a BOM or garble text: Fixed how `cm codereview` and `cm mergerequest` read comments from standard input with `--commentsfile=-` . `cm` now reads redirected and piped input the same way as a comments file passed by path, by its byte order mark or as UTF-8. Comments no longer start with a byte order mark, and non-ASCII text no longer turns into other characters on Windows consoles that don't use UTF-8. Text in the console code page, such as the output of `echo` in cmd, and text typed at the console work as before.

    • Windows
  4. Change

    All platforms - Command-line: Comments read from standard input no longer keep a BOM or garble text: Refer to cm codereview and cm mergerequest.

  5. Removal

    All platforms - Command-line: Removing a non-reviewer no longer adds a timeline event: Fixed `cm codereview reviewer remove` and `cm mergerequest reviewer remove` so they no longer add a "removed requested review" event to the timeline for users or groups that aren't reviewers. A name repeated in the same command is removed once.

  6. Change

    All platforms - Command-line: Removing a non-reviewer no longer adds a timeline event: Refer to cm codereview and cm mergerequest.

  7. Fix

    All platforms - Command-line: Built-in merge tools no longer open without interactive resolution: Fixed the built-in merge tools ( `plastic xmerge` and `plastic semanticmerge` on Windows, `plasticgui xmerge` and `plasticgui semanticmerge` on Linux and macOS) so they run in silent mode when interactive resolution is disabled. They merge the conflicts they can solve automatically, and the rest make the command fail with the pending file conflicts error. Commands on machines with no desktop, such as build agents, no longer wait for a window to close.

    • Windows
    • macOS
    • Linux
  8. Change

    All platforms - Command-line: Built-in merge tools no longer open without interactive resolution: Refer to cm merge.

  9. Fix

    macOS, Linux - Desktop GUI: The review conversation now loads with file comments that aren't on a single line: Fixed the Conversation tab of code reviews and merge requests so it loads when the review has a file comment that isn't on a single line, such as a comment on a range of lines, an image, or a whole file. A comment on a range shows its first line, and a comment with no line shows only the file path instead of "Line 0".

    • macOS
    • Linux

Pick your Unity version

Unity Releases compares releases against the version your project is on. Picking it now keeps Compare versions focused on what changes between where you are and where you might be going.