Try Serpent Free
← Salesforce DevOps Glossary

Push Upgrade

A scheduled upgrade that installs a newer package version into subscriber orgs automatically, without the subscriber initiating it.

Definition

A push upgrade lets an ISV schedule an automatic upgrade of a managed package to a newer version across some or all of its subscriber orgs, instead of waiting for each customer to install the update themselves. Push requests are scheduled through the Partner Community and typically run overnight in the subscriber's org to minimize disruption. It's most often used for patch versions, bug fixes and non-breaking changes, since Salesforce restricts pushing changes that could break existing customizations without the subscriber's awareness. Push upgrades are only available for packages, and version paths, that support upgrades in the first place; a subscriber on a much older major version may not be eligible for a direct push to the latest one. Our 2GP packaging guide covers version compatibility rules in more depth.

In practice

How it works in Serpent

Serpent tracks exactly which package version every subscriber org is running, so an ISV can see which orgs are eligible for a push upgrade and which ones need a different upgrade path before scheduling one. See DevOps for ISVs on Serpent for subscriber org version tracking.

Commit-to-package mapping in Serpent
Common questions

Push Upgrade, answered

Can a push upgrade install a major version with breaking changes?
Generally no. Push upgrades are meant for safe, backward-compatible updates; major changes usually require the subscriber to opt in and install manually.

Start free. No credit card, no install, no commitment.

Set up in under 15 minutes. No DevOps hire needed.

Curious about faster shipping before you dive in? Let's talk

Commitment free!