...
We always are sensitive to upward compatibility of our offerings and specifically want to make sure CLI scripts are as upward compatible as possible at least with the respect to those aspects that are under our control. Most of our actions remain compatible across a wide range of application releases and even to high degree across different environments (Cloud and Data Center). However, on a CLI version boundary, we do take the opportunity to remove previously deprecated support or make some changes especially where it will simplify new user experiences and remove clutter for users.
This page describes some of the important changes to be aware of when upgrading to 12.x from 11.x or earlier. If upgrading from release prior to 11.x, see also Special Compatibility Notice for ACLI Version 11.x.
Client Changes
Client | Change | Replacement | Discussion |
|---|---|---|---|
bamboo | removed | bitbucketcloud Continue to use ACLI release 11.3 | The bamboo client was deprecated in ACLI release 11.2 and now is being removed from the distribution. |
jsm | removed | Continue to use ACLI release 11.3 | The jsm client was deprecated in ACLI release 11.2 and now is being removed from the distribution. |
tempo | removed | Continue to use ACLI release 11.3 | The tempo client was deprecated in ACLI release 11.1 and now is being removed from the distribution. We were unable to provide meaningful and credible coverage of Tempo capabilities, so we have decided to discontinue the limited support we had. Our existing support in the Jira client for some Tempo custom fields will continue as normal. |
trello | removed | Continue to use ACLI release 11.3 | The trello client was deprecated in ACLI release 11.1 and now is being removed from the distribution. Low customer interest. We were unable to continue to extend our coverage of Trello capabilities, so we have decided to discontinue the support. |
segment | removed | Continue to use ACLI release 11.3 | The segment client was deprecated in ACLI release 11.1 and now is being removed from the distribution. Low customer interest. |
keen | removed | Continue to use ACLI release 11.3 | The keen client was deprecated in ACLI release 11.1 and now is being removed from the distribution. Low customer interest. |
...
Clients | Action | Change | Reason |
|---|---|---|---|
bitbucketcloud | getPullRequestList | The author columns were moved after the merge commit column on all output formats. Scripts can specify column order explicitly using the | Design oversight not conforming to standards. |
bitbucketcloud | getDownloadList |
| Clearer indication of what the column means. More consistent with other actions with a created column |
bitbucketcloud | getBranchList | Target prefix removed from commit column headers and other column changes. | Consistency with other actions and avoid confusion. |
bitbucketcloud | getUserList | User field no longer represents the deprecated Bitbucket cloud user name for older users. It is now consistently the nickname for all users. | Bitbucket deprecated the old usage for username even though it is still around for some compatibility things. It is confusing, so we settled on what Bitbucket recommends going forward. |
Deprecated Actions
This is a notice that we have deprecated some actions so you can start migrating any scripts to the new support over time. It is likely these will be removed in a later version. This was part of an ongoing effort to simplify some usage scenarios and prune our interfaces to avoid confusion.
...