Release Notes

All platforms - CLI: When you run the 'cm undo' and 'cm unco' commands in a workspace and the loaded changeset doesn't exist anymore in the server (it was deleted elsewhere), you're prompted to confirm that you'd like all your current changes rolled back and your workspace switched to the last changeset in the current branch.

The problem is that this interactive behavior produced an infinite loop when the standard input was redirected (e.g. 'cm shell' in plugins, CmdRunner, custom scripts...). We changed that so whenever the stdin is redirected, the client aborts the operation and returns an error to prevent unexpected loss of changes.

To make this compatible with unattended/batch setups (e.g. plugins) we changed the behavior of the commands so that if you include both '--all' and '--silent' as CLI arguments, the client will automatically update the workspace to the last available changeset in the branch without any user interaction or output messages.

Windows - Plastic: We noticed that Spanish users couldn't type the ']' character if they had a Diff Window opened. This happened because that character is triggered by the combination of the special key 'AltGr' of the Spanish keyboard and the '+' key. The 'AltGr' key is translated to Control + Alt, and the Diff Window has Control + '+' as the shortcut for "Next file". Therefore, the ']' character in Spanish keyboards was triggering the shortcut, rather than getting written. Kind of obscure but annoying nonetheless.

All platforms - CLI: We fixed a corner-case scenario that prevented you from removing changesets. This happened if four conditions were met:

1- You ran the command in a workspace

2- You had pending changes in your workspace

3- The head changeset of the branch loaded in the workspace had the same ChangesetID as the changeset you wanted to remove

4- The changeset you wanted to remove belonged to another repository (not the one loaded in your workspace)

In this case, you were prompted with a message notifying you that you can't remove the changeset of the current branch while there are pending changes. That didn't make sense because the changeset you selected wasn't even in the same repository.

Fixed!

All platforms - WebAdmin: The Lock Rules and Merge Rules sections in the WebAdmin Configuration area weren't displaying the appropriate information in multi-instance environments. They read/wrote config files in the server binaries directory instead of the expected shared directory for those special environments. Fixed!

macOS - Plastic, Gluon: The "Browse" button in the first steps dialog (the one we show when you don't have configured the client yet) didn't work if the path to open contained spaces. It's fixed now!

All platforms - CLI: Downloading revision contents failed if a proxy server was configured and unreachable. It will automatically retry the download against the main server now. This wasn't failing in the GUI.

Windows - Plastic: Fixed a minor aesthetic issue in the "Create Label" and "Create Attribute" dialogs. The issue was related to positioning the comment TextBox in HDPI monitors. It didn't look its best, but it does now! Just so you can appreciate the aesthetic nuisance I'm talking about, check in the picture below the before and the after - notice how the Comments TextBox is a little bigger than it should?

Windows - Plastic: Fixed a nullref error that could happen on the following scenario:

* Fresh start of Plastic GUI.

* Run a merge from another branch. On this merge, semantic merge resolves automatically a file conflict. But there is a text file conflict on another file that requires user intervention.

* Finish the merge and open the pending changes view.

* Show differences for the text file that required manual intervention causing a nullref error.

Now this error is fixed. It was just an aesthetic issue (the file contents in the merge are the correct contents).