--- schema_version: "1" id: 39e5710bd71052e1a047a2e80a016dc3a2276657f506d5205dfb913ce3f6d8a3 title: Create Versions of a Second-Generation Managed Package collection: developer version: current locale: en-us portal_url: https://docs.salesforce.com/developer/current/en-us/platform-pkg-exchange/managed_packaging/guides/second-generation/sfdx-dev-dev2gp-create-pkg-ver.md canonical_url: https://developer.salesforce.com/docs/platform/pkg2-dev/guide/sfdx-dev-dev2gp-create-pkg-ver.html source_site: developer.salesforce.com content_type: documentation content_hash: bf018d98e10abb7fd592bb8f2cbe96299ea9b8c3c7374d51ba4df664211a483b products: - Second-Generation Managed Packaging Developer Guide - merged-docs --- # 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. **tip:** Review [Advanced Project Configuration Parameters for Second-Generation Managed Packages](https://developer.salesforce.com/docs/platform/pkg2-dev/guide/sfdx-dev2gp-adv-config-file.md) for optional features that you can enable in the new package version. 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. **note:** If you use Claude Code in your development tools, you can create a new package version by describing what you want in natural language. For example, you can enter “Create a package version for ExamplePackage.” ## Create a Managed 2GP Package Version (Default Option) 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. ```nolang sf package version create --package "Expenser App" --installation-key “HIF83kS8kS7C” \ --definition-file config/project-scratch-def.json --code-coverage --wait 10 ``` **note:** When creating a package version, specify a `--wait` time to run the command. 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. 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. ```no_highlighting sf package version create report --package-create-request-id 08cxx00000000YDAAY ``` The output shows details about the request. ```nolang === Package Version Create Request NAME VALUE ───────────────────────────── ──────────────────── Version Create Request Id 08cB00000004CBxIAM Status InProgress Package Id 0HoB00000004C9hKAE Package Version Id 05iB0000000CaaNIAS Subscriber Package Version Id 04tB0000000NOimIAG Tag git commit id 08dcfsdf Branch CreatedDate 2024-05-08 09:48 Installation URL https://login.salesforce.com/packaging/installPackage.apexp?p0=04tB0000000NOimIAG ``` 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. ```nolang sf package version create list --created-last-days 0 ``` Details for each request display as shown here (IDs and labels truncated). ```nolang === Package Version Create Requests [3] ID STATUS PACKAGE2 ID PKG2 VERSION ID SUB PKG2 VER ID TAG BRANCH CREATED DATE === 08c... Error 0Ho... 08c... Success 0Ho... 05i... 04t... 2024-06-22 12:07 08c... Success 0Ho... 05i... 04t... 2024-06-23 14:55 ``` ## Async Validation 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. ```nolang sf package version create --async-validation ``` Sample Command-Line Output ```nolang Version create.... Create version status: PerformingValidations The validations for this package version are in progress, but you can now begin testing this package version. To determine whether all package validations complete successfully, run "sf package version create report --package-create-request-id 08cxx", and review the Status. Async validated package versions can be promoted only if all validations complete successfully. Successfully created the package version [08cxx. Subscriber Package Version Id: 04txx Package Installation URL: https://login.salesforce.com/packaging/installPackage.apexp?p0=04txx As an alternative, you can use the "sf package:install" command. ``` 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. ## Skip Validation 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. ```nolang sf package version create --skip-validation ``` **note:** You can't specify both skip validation and code coverage, because code coverage is calculated during validation. You also can't specify both skip validation and async validation at the same time. ## Update Details about a Managed 2GP Package Version 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. ```nolang sf package version update --package "Expenser App@1.3.0-5" --tag "git commit id 08dcfsdf" ``` After the update is complete, you’ll see output that looks like ```nolang Successfully updated the package version. 04tB0000000KPhnIAG ``` ## How Many Managed 2GP 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. ```nolang sf limits api display ``` Look for the Package2VersionCreates entry. ```nolang NAME REMAINING MAXIMUM ───────────────────────────────────── ───────── ───────── Package2VersionCreates 23 50 ```