Salesforce DX Developer Guide

How Salesforce Developer Experience Changes the Way You Work
Salesforce CLI Configuration and Tips
Project Setup
Authorization
Metadata Coverage
Scratch Orgs
Sandboxes
Development
Build and Release Your App
First-Generation Managed Packages
Second-Generation Managed Packages
What’s a Package?
Comparison of 2GP and 1GP Managed Packages
Namespaces
Package IDs and Aliases
Before You Create Second-Generation Managed Packages
Workflow for Second-Generation Packages
Configure Packages
Best Practices for Second-Generation Managed Packages
Frequently Used Packaging Operations
Create a Package
Generate the Package
Generate a Package Version
Create a Patch Version
Package Ancestors
Package Connected Apps in Second-Generation Managed Packaging
Package Upgrades in Second-Generation Managed Packaging
Code Coverage for 2GP Managed Packages
Release a Second-Generation Managed Package
Update a Package Version
View Package Details
Install a Package
Uninstall a Package
Publishing Your App on AppExchange
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

Update a 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.

If the most recent package version has been released, increment either the major, minor, or patch version number for the next package version you create.

Package version numbers use the format major.minor.patch.build. For example, if you released package 1.0.0.2, you could use 1.1.0.0, 2.0.0.0, or 1.0.1.0 for the next package version.