Create Versions of a Second-Generation Managed Package

A package version is a fixed snapshot of the package contents and related metadata. The package version is an installable, immutable artifact that 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 update the versionNumber parameter in the sfdx-project.json file. Verify that the metadata you want to change or add in the new package version is in the package’s main directory.

When you create a package version, you have three options regarding how package validations are handled.

• (Default) Complete all validations of dependencies, package ancestors, and metadata before the package version is returned.
• Perform validations asynchronously.
• Skip validation on the 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 settings that the metadata of the package version depends on.

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 sf 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).

Async validation creates a new package version before completing package validations. If your development team is using continuous integration (CI) scripts, you can leverage async validation to get an installable artifact sooner so you can start post-package creation steps.

To specify async validation, include the - -async-validation parameter.

Sample Command-Line Output

The command-line output provides you a package creation request ID that starts with 08c. To confirm whether all package validations complete successfully, use the 08cxx ID when and run sf package version create report --package-create-request-id 08cxx. Then validate that the Status is listed as Success. Async validated package versions can be promoted only if all validations complete successfully.

Skips validation of dependencies, package ancestors, and metadata during package version creation. Skipping validation significantly reduces the time it takes to create a new package version, but package versions created using skip validation can’t be promoted to the released state.

You can update most properties of a package version from the command line. For example, you can change the package version name or description. One important exception is that you can’t change the release status.

In this example, we’re adding the tag parameter and specifying the git commit ID associated with this package version.

After the update is complete, you’ll see output that looks like

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.