Release Notes
11.0.16.7665: Dec 01 2022
Command-line client: Update command improved for automation
Several adjustments have been made to the update command:
Before:
* Using the --xml option was not meant to be used in a pipeline.
* Using the --silent option was meant to trim all output.
Now:
* Using the --xml option with no file implies --silent. Informative output gets trimmed.
* Using the --silent option removes informative output only. Warning and error messages are still written through standard error output. You can silence those messages by using output redirection.
All clients: Incoming Changes respects the cloaked rules.
Before, the Incoming Changes operation downloaded the files/directories although they were under cloaked paths. This was inconsistent with the update operation behavior and with the cloaked semantics themselves.
Now, the changes under cloaked paths are skipped like the update operation does.
The Gluon Incoming changes is not affected by this behavior (cloaked rules don't make sense in Gluon) since the operation works in a different way.
All Platforms - DevOps: Jenkins plug now shows the link to the build job
The Jenkins plug now notifies the URL to the build job. This way users are able to get the details about what failed while building the task in Jenkins.
Find below a sample of this notification using a local Jenkins plug with a TrunkBot mergebot on Slack:

Command-line client: Switch command improved for automation
Several options have been added to the switch command, mirroring the update command: --silent, --verbose, --xml and --encoding.
See --usage for details:
> cm switch --usage
Command-line client: Undo controlled changes and preserve local content
Added the option -k | --keepchanges to the cm unco & cm partial unco to allow undo checkout and preserve all local changes.
It could be very useful when you have a checked-out file with some changes for testing that you don't want to check in. So, now, you can undo the checkout (that releases the lock), and preserve local changes just to continue with your local tests.
$cm status --noheader Changed Status Size Last Modified Path Checked-out 319.30 KB 1 minute ago body.png $cm unco -k c:\tmp\quake\body.png unchecked out correctly $cm status --noheader Changed Status Size Last Modified Path Changed 319.30 KB 1 minute ago body.png
The unco -k command can be applied to all kinds of controlled changes, turning them into local changes. This is complementary to using the checkout command to promote local changes into controlled ones.
*Added are left as private
*Checked-out are left as changed
*Deleted are left as locally-deleted
*Moved are left as locally-moved
Note this option is incompatible with dynamic workspaces.
All platforms - Plastic, Gluon: Improved app stability
We've improved app stability in some scenarios, preventing the app from crash when an exception is thrown
Command-line client: Update --xml now includes deleted items
Before, the --xml output of the update command was meant to only report items with added or updated revisions.
Deleted items are now included:
<UpdatedItems> <List> <UpdatedItem> <Path>/wkspaces/SuperRacing/Assets/wheels.png</Path> <User>Kit</User> <Changeset>122</Changeset> <Date>2022-11-27T20:30:44+01:00</Date> </UpdatedItem> </List> </UpdatedItems>
All platforms - Plastic: Disabled Semantic History option for unsupported text files
We've disabled Semantic History menu option in Annotate View for all unsupported text files in semantic history (for example, .txt files)

macOS - Plastic: Removed mono-based GUI's
We finally removed the mono-based GUI's that were deprecated months ago, in favor of net(core) based counterparts: plasticgui and gluon.
This way we ease the setup of the Plastic SCM GUI applications, since no more "mono/xamarin" and related dependencies will be a requirement anymore.
All platforms - Plastic: Fixed exception in diff when selecting files outside of refactor group
We fixed an error that was causing an exception to be thrown when selecting an item in the diff window that is not inside a refactor group.
Command-line client: Unrelated conflicts when applying a shelve.
The 'shelveset apply' command could show some directory conflicts that were not related to the changes/paths specified in the command.
This happened when 1) only some changes were specified to be applied from the shelveset and 2) there were more than one directory conflicts involved in the shelveset application.
The problem came because the filter used to apply only the specified changes was not applied again after resolving a directory conflict. Fixed.
Command-line client: Update command --xml and --silent options are incompatible
Before, using the --silent option allowed the XML output to be printed but affected to the contents themselves.
Now, those options are compatible. Moreover, the --xml option now implies --silent.