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
Development
Build and Release Your App
First-Generation Managed Packages
Second-Generation Managed Packages
Unlocked Packages
What’s a Package
Package-Based Development Model
Before You Create Unlocked Packages
Know Your Orgs
Create Org-Dependent Unlocked Packages (Beta)
Workflow for Unlocked Packages
Configure Packages
Create a Package
Generate the Package
Generate a Package Version
Code Coverage for Unlocked Packages
Release an Unlocked Package
Update a Package Version
Delete a Package or Package Version
View Package Details
Push a Package Upgrade (Beta)
Install a Package
Migrate Deprecated Metadata from Unlocked Packages
Uninstall a Package
Continuous Integration
Troubleshoot Salesforce DX
Limitations for Salesforce DX
PDF

Newer Version Available

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

Release an Unlocked Package

Each new package version is marked as beta when its created. As you develop your package, you may create several package versions before you create a version that is ready to be released and installed in production 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 force: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 once for each package version number, and you can’t undo this change.