50 documented changes.

Version
11.0.16.9116
Released
Jan 16, 2025
Product
Unity Version Control
Unity Version Control 11.x release notes

Unity Version Control 11.0.16.9116

Official notes

New

  1. Change

    All Platforms: Introducing Branch Hiding!

  2. Change

    All Platforms: We're excited to announce a long-awaited feature: the ability to hide branches! This new capability lets you focus on what's important by removing unwanted branches from your views.

  3. Change

    All Platforms: == How it works? ==

  4. Change

    All Platforms: Hiding branches happens at the server level, meaning once a branch is hidden, it disappears from the Branch Explorer, Branches View, and even the Changesets View for all users of the repository. However, the branch and its content still exist in the repository, so you can unhide or use it whenever needed.

  5. Change

    All Platforms: == Who can hide or unhide branches? ==

  6. Change

    All Platforms: Any user with "change" permission on a specific branch can hide or unhide it. This ensures flexibility while maintaining appropriate access control.

  7. Change

    All Platforms: == When to use Branch Hiding? ==

  8. Change

    All Platforms: Sometimes, you may ask us to delete branches, but this isn't always possible — e.g., when a branch has been integrated. In these cases, the Desktop GUI will now offer the option to hide those branches instead, helping you keep your workspace organized without permanently removing data.

  9. Change

    All Platforms: == A note on visibility ==

  10. Change

    All Platforms: While hiding a branch removes it from immediate views, the branch and its content remain intact in the repository. This ensures that no data is lost, and you can retrieve or unhide the branch at any time.

  11. Change

    All Platforms: You can hide or unhide branches using either the command line or the Desktop GUI:

  12. Change

    All Platforms: == Command Line: How to use Branch Hiding? ==

  13. Change

    All Platforms: Use the following commands to hide or unhide branches. For additional details, include the --help option.

  14. Change

    All Platforms: == Desktop GUI: How to use Branch Hiding? ==

  15. Change

    All Platforms: A simple and intuitive way to hide/unhide branches is also available directly within the GUI.

  16. Change

    All Platforms: From the Branch Explorer or Branches View, there's a new option available to Hide a branch:

  17. Change

    All Platforms: Note you can use "Ctrl-H" as shortcut!

  18. Change

    All Platforms: To see all the hidden branches, you can go to the Branches View and click on the new 'Show hidden branches' button:

  19. Change

    All Platforms: If you use this feature together with display filters, the hidden branches take them into account, making it easier to find the right branch based on your search criteria:

  20. Change

    All Platforms: When showing the hidden branches, there's a new option available to Unhide a branch.

  21. Change

    All Platforms: We're confident this feature will make managing your repositories more streamlined and efficient. Try it out and enjoy a clutter-free experience in Plastic SCM!

  22. Change

    Windows - Installer Update: Remove discontinued plugins

    • Windows
  23. Change

    Windows - Installer Update: We're excited to share an important update! We've optimized the installer by removing discontinued plugins and upgrading older .NET Framework applications to .NET. This change has cut the installer size by more than half, making installation faster and more efficient.

    • Windows
  24. Change

    Windows - Installer Update: == What’s Changing? ==

    • Windows
  25. Change

    Windows - Installer Update: We're discontinuing support for the following legacy Unity Version Control (UVCS) plugins:

    • Windows
  26. Change

    Windows - Installer Update: == Why are we making this change? ==

    • Windows
  27. Change

    Windows - Installer Update: These plugins no longer align with our vision for delivering a streamlined, modern product. By focusing on core improvements, we'll deliver updates faster and enhance the overall user experience.

    • Windows
  28. Change

    Windows - Installer Update: == What should you do? ==

    • Windows
  29. Fix

    Windows - Installer Update: We strongly recommend upgrading to the latest version of UVCS to enjoy the latest improvements, performance boosts, and bug fixes.

    • Windows
  30. Change

    Windows - Installer Update: If you rely on the discontinued plugins, you can keep using them by staying on your current UVCS version. However, please note:

    • Windows
  31. Change

    Windows - Installer Update: Thank you for your understanding and for being part of our journey to improve Unity Version Control. If you have any questions or concerns, feel free to reach out to our support team—we're here to help!

    • Windows
  32. Change

    All platforms: GitSync handles the .lfsconfig URL setting

  33. Change

    All platforms: GitSync now takes into account the .lfsconfig configuration file. It looks for the URL setting in order to use the specified URL for the LFS blobs download/upload (instead of always using the default one).

  34. Change

    All platforms: This allows you to import repositories from Git (to UVCS) that used a custom URL for the LFS blobs though the .lfsconfig file.

  35. Change

    All platforms: It only accepts HTTP/HTTPS URLs at the moment:

Windows - Installer Update

  1. Change

    Visual Studio Integration

  2. Change

    Shell Extension

  3. Change

    SCC Plugin

  4. Change

    Microsoft Office Integration

  5. Change

    These plugins will no longer be maintained or supported.

  6. Change

    Compatibility or functionality issues may arise in the future.

Bug

  1. Fix

    All clients: Fixed "Unable to cast object" error checking in a file under an Xlink

  2. Change

    All clients: This error only happened under very specific circumstances:

  3. Fix

    All clients: Now it's fixed.

  4. Change

    All platforms - Gluon: File conflicts not properly detected applying a shelveset

  5. Change

    All platforms - Gluon: The Gluon shelveset application didn't promote the changes to file conflicts when the file was not modified in the workspace and the workspace revision didn't match with the base revision of the change. This way, it applied directly the shelveset change content to the workspace, losing all the changes introduced later in the file.

  6. Change

    All platforms - Gluon: Now, it properly detects the file conflict and merges the workspace changes with the shelve changes.

All clients

  1. Change

    You have a file checked-out under an Xlink with a fs protection set from Linux/macOS.

    • macOS
    • Linux
  2. Change

    There are new changes only in the root repo, so you need to run an Incoming Changes operation before running the check-in.

  3. Change

    After that, the check-in operation throws the error: Unable to cast object of type 'Codice.CM.Common.Tree.CheckinItemData' to type 'Codice.Client.Commands.CheckIn.ClientCheckinItemData'.

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.