Second-Generation Managed Packaging Developer Guide

Advanced Features for Second-Generation Managed Packages

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.

Advanced Features for Second-Generation Managed Packages

After you're comfortable with creating second-generation managed packages, learn about these advanced features to customize your package development processes.

Package Ancestors for Second-Generation Managed Packages
Second-generation managed packaging (managed 2GP) offers a flexible package versioning model that lets you break your linear versioning and abandon a package version you no longer want to build upon. We call these versioning decisions package ancestry.
Patch Versions for Second-Generation Managed Packages
Patch versions are a way to fix small issues with your second-generation managed package without introducing major feature changes. Customers who are using an older version of your package can install a patch and not be forced to upgrade to a new major package version.
Create Dependencies Between Second-Generation Managed Packages
To avoid monolithic package development practices, plan to develop smaller, modular packages that group similar functionality and components. You can then define the dependencies between these packages. A package dependency is when metadata contained in one package depends on metadata contained in another package. For example, defining dependencies allow you to extend the functionality of a base package with components and metadata located in a separate package.
Considerations for Promoting Packages with Dependencies
If your company is developing a package that has a package dependency, ask yourself these questions before promoting (releasing) a new package version.
Advanced Project Configuration Parameters for Second-Generation Managed Packages
As your managed 2GP package development becomes more complex, consider including these optional parameters in your sfdx-project.json file.
Second-Generation Managed Packaging Keywords
A keyword is a variable that you can use to specify a package version number.
Target a Specific Release for Your Second-Generation Managed Packages During Salesforce Release Transitions
During major Salesforce release transitions, you can specify preview or previous when creating a package version. Specifying the release version for a package allows you to test upcoming features, run regression tests, and support customers regardless of which Salesforce release their org is on. Previously, you could only create package versions that matched the Salesforce release your Dev Hub org was on.
Use Branches in Second-Generation Managed Packaging
Development teams who use branches in their source control system (SCS), often build package versions based on the metadata in a particular branch of code.
Specify Unpackaged Metadata or Apex Access for Package Version Creation Tests for Second-Generation Managed Packages
For scenarios where you require metadata that isn’t part of your second-generation managed package, but is necessary for Apex test runs, you can specify the path containing unpackaged metadata in the sfdx-project.json file. The unpackaged metadata isn’t included in the package and isn’t installed in subscriber orgs.
Package IDs and Aliases for Second-Generation Managed Packages
During the package lifecycle, packages and package versions are identified by an ID or package alias. When you create a second-generation managed package or package version, Salesforce CLI creates a package alias based on the package name, and stores that name in the packageAliases section of the sfdx-project.json file. When you run CLI commands or write scripts to automate packaging workflows, it’s often easier to reference the package alias, instead of the package ID or package version ID.
Avoid Namespace Collisions in Second-Generation Managed Packages
Namespaces impact the combination of package types that you can install in an org.
Remove Metadata Components from Second-Generation Managed Packages
Remove metadata components such as Apex classes that you no longer want in your second-generation managed packages.
Delete a Second-Generation Managed Package or Package Version
Use the sf package version delete and sf package delete commands to delete packages and package versions that you no longer need.
Frequently Used Packaging Operations for Second-Generation Managed Packages
Transfer a Second-Generation Managed Package to a Different Dev Hub
You can transfer the ownership of a second-generation managed package (managed 2GP) from one Dev Hub org to another. These transfers can occur either internally between two Dev Hub orgs your company owns, or you can transfer a package externally to another Salesforce Partner or ISV. This change provides a way to sell a managed 2GP package to a different company.
Contact Salesforce Partner Support to Enable Specific Packaging Features
Certain packaging features can only be enabled by Salesforce Partner Support.