Second-Generation Managed Packaging Developer Guide
jNote: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.
Push a Package Upgrade for Second-Generation Managed Packages
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.