Unity Version Control 11.0.16.10484

Bug

1. Fix

   Windows - All clients: Fixed failure when renewing an expired token in parallel: When several commands renewed an expired token at the same time, some of them failed with "The process cannot access the file '...\tokens.conf' because it is being used by another process."

   • Windows
2. Fix

   Windows - All clients: Fixed failure when renewing an expired token in parallel: This happened, for example, when a client ran several `cm` commands at startup.

   • Windows
3. Fix

   Windows - All clients: Fixed failure when renewing an expired token in parallel: Now, a command that saves `tokens.conf` waits while another process is reading it, so the save no longer fails.

   • Windows
4. Fix

   All platforms - SemanticMerge: Fixed automatic merge dropping members of a new interface: An automatic semantic merge could leave a newly added interface empty by silently dropping its member declarations without reporting a conflict. This happened when the source contributor also moved a member from one interface to another.

5. Fix

   All platforms - SemanticMerge: Fixed automatic merge dropping members of a new interface: The merge now keeps the members of the new interface.

6. Fix

   All platforms - Server: Fixed initial check-in with a custom blobspath: Before, the first check-in to a newly created repository failed when setting `blobspath` in `jet.conf` to a path outside the server's default storage, such as a dedicated disk or a network share. The server created the repository's metadata folder but not the matching blob folder at the custom location, so it couldn't write the blob index file and the check-in failed.

7. Fix

   All platforms - Server: Fixed initial check-in with a custom blobspath: The server now creates the repository's blob folder when the repository is created, so the initial check-in succeeds with any `blobspath` . Repositories using the default (empty) `blobspath` are unaffected.