After your testing is done, your app is almost ready to be published in your enterprise or on AgentExchange. Generate a new managed package version in your Dev Hub org.
Before You Begin
Ensure that you’ve authorized the packaging org and can view the existing package versions.
1sf org login web --instance-url https://test.salesforce.com --set-default org_alias
View the existing package versions for a specific package to get the ID for the version you want to install.
1sf package1 version list --package-id 033...
To view details for all packages in the packaging org, run the command with no parameters.
More than one beta package can use the same version number. However, you can use each version number for only one managed package version. You can specify major or minor version numbers.
You can also include URLs for a post-installation script and release notes. Before you create a managed package, make sure that you’ve configured your developer settings, including the namespace prefix.
After you create a managed package version, you can’t change some attributes of Salesforce components used in the package. See: Components Available in Managed Packages for information on editable components.
Note
Create the managed package. Include the --managed-released parameter.
You can use other options, like --wait to specify the number of minutes to wait.
To protect the package with an installation key, include a value for --installation-key. Then, you or a subscriber must supply the key before you can install the package in a target org.
After the managed package version is created, you can retrieve the new package version ID using sf package1 version list.
j