Second-Generation Managed Packaging Developer Guide
jNewer Version Available
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.
Before you promote the package version, ensure that the user permission, Promote a package version to released, is enabled in the Dev Hub org associated with the package. Consider creating a permission set with this user permission, and then assign the permission set to the appropriate user profiles.
When you’re ready to release, use sf package version promote.
If the command is successful, a confirmation message appears.
After the update succeeds, view the package details.
Confirm that the value of the Released property is true.
You can promote and release only one time for each package version number, and you can’t undo this change.