Unity Version Control 11.0.16.9271
11 documented changes.
- Version
- 11.0.16.9271
- Released
- Mar 13, 2025
- Product
- Unity Version Control
Unity Version Control 11.0.16.9271
New
- Change
All Platforms - Desktop GUI: Support for legacy workspaces in upcoming organization migration (more info here, in our dedicated technical documentation)
- Change
All Platforms - Desktop GUI: This update prepares the Desktop GUI for the upcoming migration from legacy cloud organizations to unified Unity organizations. Changes have been implemented to ensure that workspaces created using the legacy format will remain visible in the repositories list, and they will be properly linked to their repositories after the migration.
- Change
All Platforms - Desktop GUI: Users can expect a smooth transition with backward compatibility for existing workspaces when the migration takes place later this year.
Bug
- Improvement
All Platforms - Desktop GUI: Workspace Explorer context menu wrongly updated
- Change
All Platforms - Desktop GUI: The 'New' and 'Change revision type' context menu options were incorrectly computed using the previously right-clicked item instead of the current one.
- Fix
All Platforms - Desktop GUI: Right-clicking a directory followed by a file could allow unintended options like "New" to be available. The behavior has been fixed! The context menu now correctly updates based on the currently selected item.
- Change
Command-line client: Prevent credentials prompt for @unity organizations when using username/password or token
- Fix
Command-line client: We've fixed an issue affecting the command line client when determining the datacenter for the new unified organizations ( `name@unity` ).
- Change
Command-line client: This update ensures a smoother experience when working with `@unity` organizations by correctly handling authentication in all cases.
Command-line client
- Change
When running `cm configure` in non-interactive mode, the provided username/password or token will now be correctly used to resolve the datacenter. This prevents the client from stalling due to unnecessary credential prompts.
- Fix
For all other commands, if credentials are explicitly provided (via username/password or token), they will also be used to resolve the datacenter. This fixes the previous behavior where the command would fail with an error.