Push a Package Upgrade for Second-Generation Managed Packages
Push upgrades enable you to upgrade second-generation managed packages installed in subscriber orgs, without asking customers to install the upgrade themselves. You can choose which orgs receive a push upgrade, what version the package is upgraded to, and when you want the upgrade to occur. Push upgrades are helpful if you need to push a change for a hot bug fix.
Use Salesforce CLI or SOAP API to initiate the push upgrade, track the status of each job, and review error messages if any push upgrades fail.
The push upgrade feature is only available to first- and second-generation managed packages that have passed the AgentExchange security review. The CLI push upgrade commands are available to second-generation managed packages and unlocked packages. To enable push upgrades for your managed package, log a case with Salesforce Partner Support. For details on the security review process, see Pass the AgentExchange Security Review in the ISVforce Guide.
Package Type
Push Upgrade using CLI?
Push Upgrade using API?
Push Upgrade using UI?
2GP
Yes
Yes
No
1GP
No
Yes
Yes
Unlocked
Yes
Yes
No
Push Upgrade Considerations for Second-Generation Managed Packages
You can push upgrades to packages that have passed AgentExchange security review only.
The same manageability rules for package version upgrades are applicable to push upgrades.
When a push upgrade is installed, the Apex in package is compiled.
Push upgrades can be used even if the package version requires a password.
Use Salesforce CLI commands to schedule, abort, or view details about your push upgrade requests. Push upgrades let you upgrade second-generation managed packages installed in subscriber orgs, without asking customers to install the upgrade themselves.
In certain scenarios, a Salesforce customer may require the ability to block push upgrades of managed packages that they have installed in their org. Customized push upgrades let Salesforce Partners give customers the ability to restrict push upgrades to a specific customer org for a specific package.
Determine how to provide existing non-admin users access to new and changed features. By default, any new components included in the push upgrade package version are assigned only to admins.
Push Upgrade is one of the most powerful features we provide to our partners. Pushing an upgrade without proper planning and preparation can result in significant customer satisfaction issues. Here are some best practices to consider.
j