Note: 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.

Understanding Package Upgrades with Ancestry

Review how package ancestry impacts which package version upgrades are allowed.

Refer to this table and the package ancestry tree to understand whether your subscribers can upgrade between these 2GP package versions.

Example Package Ancestry Tree

Upgrade From	Upgrade To	Will This Package Upgrade Succeed?
1.1	1.7	Yes
1.3.2	1.3.4	Yes. Both 1.3.2 and 1.3.4 are patch versions within the same major and minor version. You’re allowed to upgrade between patch versions that share the same major and minor version.
1.3.1	1.7	Yes. 1.3.1 is a patch version. Because upgrading from 1.3 to 1.7 is allowed, you can also upgrade from 1.3.x to 1.7.
1.2	1.3	No. These two versions don’t share an ancestry path.
1.5	1.7	No. These two versions don’t share an ancestry path.
1.4	1.3.3	No. Downgrading an installed package isn’t allowed.
1.0	1.8	Yes