Unity Version Control 11.0.16.9343
29 documented changes.
- Version
- 11.0.16.9343
- Released
- Apr 10, 2025
- Product
- Unity Version Control
Unity Version Control 11.0.16.9343
New
- Change
DevOps Mergebots: Jira plug now writes the Release Date field on new version creation
- Change
DevOps Mergebots: From now on, the Jira integration for Mergebots writes the "Release Date" field on "createrelease" action (new Jira version creation).
- Change
DevOps Mergebots: Before, just the version name and description were set.
- Improvement
All Platforms - Desktop GUI: Improved support for workspace-related actions in Plastic links
- Change
All Platforms - Desktop GUI: When opening a Plastic link, the application now enables workspace-related actions—such as diff, undelete, history, and annotate—in the Diff or Code Review window. It automatically selects the most recent workspace associated with the Plastic link's repository. If no workspace is found, these actions are just disabled (as previously) to ensure a consistent user experience.
- Feature
All platforms - Desktop GUI and Gluon: Added option to diff the changeset of moved and deleted history items
- Change
All platforms - Desktop GUI and Gluon: Before, accessing the changeset diff was only possible for history items that represented new revisions with actual changes.
- Change
All platforms - Desktop GUI and Gluon: Now you can quickly open the diff tool in the history view from a moved or deleted item out of convenience.
Bug
- Change
Command-line client: Fix for incorrect .plastic renaming issue
- Change
Command-line client: Previously, it was possible to delete a file and then use the `cm move` command to rename another file as the workspace configuration directory ( `.plastic` by default):
- Change
Command-line client: Example of the sequence that causes the problem:
- Change
Command-line client: While the file wasn't actually renamed on disk and the directory remained intact, this behavior was unintended and could cause confusion.
- Change
Command-line client: From now on, renaming any file to `.plastic` won't be possible (to prevent reaching an inconsistent workspace status) and will show the following controlled error message instead:
- Change
Command-line client: Fix 'no such user or group' error when editing the ACLs
- Change
Command-line client: When using the `cm acl` command, users and groups were wrongly solved against your default server (the one set up in your client.conf file). This led to errors or unexpected behavior when targeting a different repository.
- Change
Command-line client: Fix 'no such user or group' error when setting the owner of an object
- Change
Command-line client: When using the `cm setowner` command, users and groups were wrongly solved against your default server (the one set up in your client.conf file). This led to errors or unexpected behavior when targeting a different repository.
- Improvement
Command-line client: Improved GitHub LFS Syncing
- Fix
Command-line client: We have fixed an issue when syncing GitHub repositories containing large files (over 2 GB) using the command-line client.
- Change
Command-line client: With this fix, the cm sync command now handles pulling files exceeding 2 GB.
- Fix
All Platforms - Desktop GUI: Fixed Branch Explorer Label menu
- Fix
All Platforms - Desktop GUI: Fixed an issue where label context menu actions in the Branch Explorer (rename, delete, etc.) worked only the first time, then stopped responding on subsequent attempts. All label menu items now function consistently for multiple operations.
- Change
All platforms - Desktop GUI: Incorrect Error Message
- Fix
All platforms - Desktop GUI: Fixed an issue where an incorrect error message was shown when attempting to apply changes from a shelf.
- Change
All platforms - Desktop GUI: The error message now correctly describes the issue, providing accurate information about what went wrong.
- Change
All Platforms - Desktop GUI: Double-clicking a file from a Plastic link causes an error
- Fix
All Platforms - Desktop GUI: Previously, double-clicking a file in a Plastic link (e.g., in code reviews or branches) caused a NullReferenceException. This issue has been resolved by ensuring the application verifies whether the diff action is available before executing the double-click operation.
- Change
All platforms - Plugin for JetBrains IDEs: Branch detection after external switch
- Fix
All platforms - Plugin for JetBrains IDEs: Fixed an issue where the IDE failed to detect the current branch correctly after the workspace branch was switched externally.