Packages can have one or more versions, and you can deploy and promote any version of a package.
For example, a Pega Robot Studio developer can publish an initial 1.0 package, which has been deployed to a production level. The developer can later publish an updated 1.1 package, which you can deploy to your QA level, where you can test it and then deploy it to production users.
- Automation packages
After you build an automation, you can publish automation packages to a Package Server and then to Pega Robot Manager, which displays all the available packages that developers can publish.