Second-Generation Managed Packaging Developer Guide

Second-Generation Managed Packages
What’s a Second-Generation Managed Package?
Set Up Your Development Environment
Before You Create Second-Generation Managed Packages
Know Your Orgs for Second-Generation Managed Packages
Link a Namespace to a Dev Hub Org
Namespaces for Second-Generation Managed Packages
Create and Register Your Namespace for Second-Generation Managed Packages
Key Concepts in Second-Generation Managed Packaging
How Manageability Rules and Ancestry Impact Upgrades for Second-Generation Managed Packages
Which Package Types Can Your Package Depend On?
Scratch Orgs and Package Development
Workflow for Second-Generation Managed Packages
Components Available in Second-Generation Managed Packages
Behavior of Specific Metadata in Second-Generation Managed Packages
Develop Second-Generation Managed Packages
Install and Uninstall Second-Generation Managed Packages
Prepare to Distribute Your Second-Generation Managed Package
Push a Package Upgrade for Second-Generation Managed Packages
Advanced Features for Second-Generation Managed Packages
Best Practices for Second-Generation Managed Packages
Manage Licenses for Managed Packages
Manage Features in Second-Generation Managed Packages
Get Started with AgentExchange App Analytics
Gaps Between First-Generation and Second-Generation Managed Packaging
PDF

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.

Which Package Types Can Your Package Depend On?

Both second-generation managed packaging (managed 2GP) and unlocked packaging let you easily develop small interdependent packages and share logic between them. If you design your app to rely on small modular packages, both package creation and package installation are faster, and you’re less likely to hit limits.

To develop small, modular packages, you create dependencies between your packages. A package dependency is when metadata contained in one package depends on metadata contained in another package. These dependencies allow you to extend the functionality of the base package with components and metadata in a separate extension package.

When working with packaging, only certain combinations of packages are supported.

Can a Managed 1GP Depend on a ... Can a Managed 2GP Depend on a ... Can an Unlocked Package Depend on a ... Can an Unmanaged Package Depend on a ...
Managed 1GP Yes Yes Yes No
Managed 2GP No1 Yes Yes No
Unlocked package Not recommended Not recommended Yes No
Unmanaged package Not recommended Not recommended Not recommended No

1This dependency isn’t supported, and we block the installation of managed 2GP packages in managed 1GP packaging orgs. We can override this behavior on an individual basis. To share your scenario and request an override, log a case with Salesforce Partner Support. We’re investigating how to support this dependency scenario more broadly.