Customized push upgrades enable partners and customers to manage the push upgrade lifecycle. With this feature, partners can grant select customers the ability to block push upgrades. Customized push upgrades are especially useful for highly regulated environments where strict compliance and validation protocols require control of upgrade timing and version oversight. This feature provides the granular control necessary to ensure compliance and system stability during version transitions.
Where: This change applies to second- and first-generation managed packages.
Who: To manage customized push upgrades, users need the permissions to perform packaging push upgrades.
Why: In highly regulated industries like healthcare or finance, an unannounced automated upgrade can disrupt validated workflows or trigger compliance audits. Customized push upgrades allow you to test new package versions in a sandbox environment before scheduling the production push at a time that minimizes operational risk.
See Also
- Second-Generation Managed Packaging Developer Guide: Enable a Package Subscriber to Restrict Push Upgrades
- Second-Generation Managed Packaging Developer Guide: Push a Package Upgrade for Second-Generation Managed Packages
- First-Generation Managed Packaging Developer Guide: Enable a Package Subscriber to Restrict Push Upgrades
- First-Generation Managed Packaging Developer Guide: Push Package Upgrades to Subscribers