Review the updates in released versions of the Azure DevOps package such as new and enhanced features as well as fixes and limitations. The page also lists the release dates of each version, and the compatible Control Room and Bot Agent versions.
Version summary
The following table lists the versions of Azure DevOps package released either with an Automation 360 release or as a package-only release (in descending order of release dates). Click the version link for information about updates in that package version.
| Version | Release date | Release type | Bot Agent version | Control Room build |
|---|---|---|---|---|
| 1.1.3 | 29 September 2026 | Package-only; post Automation 360 v.41 release | 22.240.34 or later | 45892 or later |
| 1.0.2 | 7 July 2026 | Package-only; post Automation 360 v.40 release | 22.240.34 or later | 45892 or later |
| 1.0.1 | 11 May 2026 | Package-only; post Automation 360 v.40 release | 22.240.34 or later | 45892 or later |
- To download an individual package (updated in an Automation 360 release where you want only the package), use this
URL:
https://aai-artifacts.my.automationanywhere.digital/packages/<package-file-name>-<version.number>.jar - For Azure DevOps
package, the naming convention is:
bot-command-azure-devops-<version.number>.jarFor example,
bot-command-azure-devops-1.0.0.jar
For detailed steps on downloading a package and manually adding it to the Control Room, see Adding a package to the Control Room.
1.1.3
- Compatible Bot Agent version: 22.240.34 or later
- Compatible Control Room version: 45892 or later
| What's new |
|---|
| Test management support in Azure DevOps
package The Azure DevOps package now includes actions for managing test plans, test suites, test cases, test runs, and test points. You can use these actions to automate key test management tasks, including creating and organizing test structures, executing test runs, and updating test points, without switching to the Azure DevOps portal. |
| OAuth 2.0 support in Connect action The Azure DevOps package now supports Control Room managed OAuth 2.0 authentication to establish an authenticated session with an Azure DevOps instance. Microsoft is retiring Personal Access Tokens (PATs) on December 1, 2026. Use OAuth 2.0 authentication to switch from PAT before the retirement date. For more information on deprecation, see Upcoming feature deprecation. |
1.0.2
- Compatible Bot Agent version: 22.240.34 or later
- Compatible Control Room version: 45892 or later
| Fix |
|---|
| Fixed an issue where the bot returned a runtime error when a pipeline repository name contained spaces. |
1.0.1
- Compatible Bot Agent version: 22.240.34 or later
- Compatible Control Room version: 45892 or later
| What's new |
|---|
| New Azure DevOps
package support You can use the Azure DevOps package to automate CI/CD pipeline operations from Automation 360. The package authenticates with Azure DevOps using a Personal Access Token, and provides actions to manage the full pipeline lifecycle across your organization and project. |
| Known limitation |
|---|
When creating a pipeline, ensure the repository name does not contain spaces. The Azure DevOps API treats spaces as invalid characters in repository names, which causes the bot to return an error at runtime. Workaround: When you create a project in Azure DevOps, you must not create a project name with space. |