Second-Generation Managed Packaging Developer Guide
jNewer Version Available
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.
| Upgrade From | Upgrade To | Will This Package Upgrade Succeed? |
|---|---|---|
| 0.2.0.1 | 0.3.4.3 | Yes |
| 0.1.0.3 | 0.3.5.2 | Yes |
| 0.3.3.6 | 0.3.5.2 | Yes. Ancestry isn’t enforced for patch version upgrades that occur between package versions that share the same major and minor package version numbers. In this example, both versions begin with 0.3. |
| 0.2.0.1 | 1.2.0.3 | Yes |
| 0.3.0.1 | 0.1.0.3 | No. Downgrading an installed package isn’t allowed. |
| 0.3.4.3 | 0.3.3.6 | No. Downgrading an installed package isn’t allowed. |
| 1.2.0.3 | 1.3.0.7 | No. To upgrade to 1.3.0.7, package version 1.2.0.3 must be the specified ancestor, or the specified ancestor must be a descendent of 1.2.0.3. |
Example Package Ancestry Tree
