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

Generate a Package Version

A package version is a fixed snapshot of the package contents and related metadata. The package version lets you manage changes and track what’s different each time you release or deploy a specific set of changes.

Before you create a package version, first verify package details, such as the package name, dependencies, and major, minor, and patch version numbers, in the sfdx-project.json file. Verify that the metadata you want to change or add in the new package version is located in the package’s main directory.

How Many Package Versions Can I Create Per Day?

Run this command to see how many package versions you can create per day and how many you have remaining.

Look for the Package2VersionCreates entry.

Create a Package Version

Create the package version with this command. Specify the package alias or ID (0Ho). You can also include a scratch definition file that contains a list of features and setting that the metadata of the package version depends on.

When creating a package version, specify a --wait time to run the command in non-asynchronous mode. If the package version is created within that time, the sfdx-project.json file is automatically updated with the package version information. If not, you must manually edit the project file.

Note

It can be a long-running process to create a package version, depending on the package size and other variables. You can easily view the status and monitor progress.

The output shows details about the request.

You can find the request ID (08c) in the initial output of force:package:version:create.

Depending on the size of the package and other variables, the create request can take several minutes. When you have more than one pending request to create package versions, you can view a list of all requests with this command.

Details for each request display as shown here (IDs and labels truncated).

Skip Validation to Quickly Iterate Package Development

Iterate package development more efficiently by skipping validation of dependencies, package ancestors, and metadata during package version creation. Skipping validation reduces the time it takes to create a new package version, but you can promote only validated package versions to the released state.

In Tooling API, use the SkipValidation field on the Package2VersionCreateRequest object.

You can't specify both skip validation and code coverage, because code coverage is calculated during validation.

Note