Second-Generation Managed Packaging Developer Guide
Workflow for Second-Generation Managed Packages
Code Coverage for Second-Generation Managed Packages
Package Installation Key for Second-Generation Managed Packages
Release a Second-Generation Managed Package
Share Release Notes and Post-Install Instructions for Second-Generation Managed Packages
Publishing Your App on AppExchange
Best Practices for Second-Generation Managed Packages
Gaps Between First-Generation and Second-Generation Managed Packaging
Newer Version Available
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
AppExchange.
-
Code Coverage for Second-Generation Managed Packages
Before you can release and distribute a second-generation managed package version on AppExchange, 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 AppExchange 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 AppExchange
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 AppExchange partner console, all your released managed 2GP package versions are visible in the partner console.