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
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
Package Ancestors for Second-Generation Managed Packages
Understanding Package Upgrades with Ancestry
View Package Ancestry
Patch Versions for Second-Generation Managed Packages
Create Dependencies Between Second-Generation Managed Packages
Considerations for Promoting Packages with Dependencies
Advanced Project Configuration Parameters for Second-Generation Managed Packages
Second-Generation Managed Packaging Keywords
Target a Specific Release for Your Second-Generation Managed Packages During Salesforce Release Transitions
Use Branches in Second-Generation Managed Packaging
Specify Unpackaged Metadata or Apex Access for Package Version Creation Tests for Second-Generation Managed Packages
Package IDs and Aliases for Second-Generation Managed Packages
Avoid Namespace Collisions in Second-Generation Managed Packages
Remove Metadata Components from Second-Generation Managed Packages
Delete a Second-Generation Managed Package or Package Version
Frequently Used Packaging Operations for Second-Generation Managed Packages
Transfer a Second-Generation Managed Package to a Different Dev Hub
Contact Salesforce Partner Support to Enable Specific Packaging Features
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.

View Package Ancestry

Use Salesforce CLI commands to quickly confirm your package’s ancestor, or to create a visualization of the package ancestry tree.

View Package Ancestor Details in Salesforce CLI

Use the sf package version report or sf package version list command to view the name and version number of the package ancestor.

Output from sf package version report command.

Output from package:version:list command

Output from sf package version list command.

Output from package:version:report command

Visualize Package Ancestry

Use the displayancestry CLI command to create visualizations of your package or package version’s ancestry tree. You can view the visualization in Salesforce CLI or use the dot-code parameter to generate output that can be used in graph visualization software.

Use sf package version displayancestry to quickly visualize your package ancestry and understand the possible package upgrade paths.

Graphic tree visualization for package:version:create

Graphic tree visualization for package:create

To generate dotcode output, specify sf package version displayancestry --dot-code.