Second-Generation Managed Packaging Developer Guide

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.

Prepare to Distribute Your Second-Generation Managed Package

Before you release a version of your second-generation managed package, ensure that you understand the code coverage requirements, release logistics, and how to publish your app on AgentExchange.

Code Coverage for Second-Generation Managed Packages
Before you can release and distribute a second-generation managed package version on AgentExchange, the Apex code must meet a minimum 75% code coverage requirement. And every Apex Trigger in a package needs test coverage.
Package Installation Key for Second-Generation Managed Packages
To ensure the security of the metadata in your second-generation managed package, you must specify an installation key when creating a package version. Package creators provide the key to authorized subscribers so they can install the package. Package installers provide the key during installation, whether installing the package from the CLI or from a browser. An installation key is the first step during installation. The key ensures that no package information, such as the name or components, is disclosed until the correct installation key is supplied.
Release a Second-Generation Managed Package
Each new second-generation managed package version is marked as beta when created. As you develop your package, you may create several package versions before you create a version that is ready to be released and distributed. Only released package versions can be listed on AgentExchange and installed in customer orgs.
Share Release Notes and Post-Install Instructions for Second-Generation Managed Packages
Share details with your subscribers about what’s new and changed in a released second-generation managed package.
Publishing Your App on AgentExchange
If you’ve published a first-generation managed package, you’ll notice the process for publishing a second-generation managed package (managed 2GP) is different. After you link your Dev Hub org to the AgentExchange partner console, all your released managed 2GP package versions are visible in the partner console.
Recommend a Specific Package Version to Your Subscribers
You can choose to recommend that your subscribers upgrade to a specific, released version of your package.