Salesforce DX Developer Guide

How Salesforce Developer Experience Changes the Way You Work
Enable Dev Hub Features in Your Org
Project Setup
Authorization
Metadata Coverage
Scratch Orgs
Sandboxes
Track Changes Between Your Project and Org
Development
Build and Release Your App
First-Generation Managed Packages
Build and Release Your App with Managed Packages
Packaging Checklist
Deploy the Package Metadata to the Packaging Org
Create a Beta Version of Your App
Install the Package in a Target Org
Create a Managed Package Version of Your App
View Information About a Package
Second-Generation Managed Packages
Unlocked Packages
Continuous Integration
Troubleshoot Salesforce DX
Limitations for Salesforce DX
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Create a Managed Package Version of Your App

After your testing is done, your app is almost ready to be published in your enterprise or on AppExchange. Generate a new managed package version in your Dev Hub org.
Ensure that you’ve authorized the packaging org and can view the existing package versions.
1sfdx auth:web:login --instanceurl https://test.salesforce.com --setdefaultusername org_alias
View the existing package versions for a specific package to get the ID for the version you want to install.
1sfdx force:package1:version:list --packageid 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. The ISVforce Guide has information on editable components.

Note

  1. Create the managed package. Include the --managedreleased parameter. 
    1sfdx force:package1:version:create --packageid 033xx00000007oi --name ”Spring 17” --description ”Spring 17 Release” --version 3.2 --managedreleased
    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 --installationkey. 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 force:package1:version:list.