Skip to main content

Table of Contents

Package versions


Only available versions of this content are shown in the dropdown

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.

Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us