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
Track Changes Between Your Project and Org
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
Push a Package Upgrade
Install a Package
Install Packages with the CLI
Install Packages from a URL
Upgrade a Package Version
Sample Script for Installing Packages with Dependencies
Uninstall a Package
Publishing Your App on AppExchange
Gaps Between First-Generation and Second-Generation Managed Packaging
Test and Respond to the New Order Save Behavior
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

Upgrade a Package Version

Are you introducing metadata changes to an existing package? You can use the CLI to upgrade one package version to another.
When you perform a package upgrade, here’s what to expect for metadata changes.
  • Metadata introduced in the new version is installed as part of the upgrade.
  • Metadata modified in the new version is updated as part of the upgrade.
  • Metadata removed in the new version is deleted as part of the upgrade.

To upgrade a package version, the new version must be a direct descendent of the package version installed in your org. See Package Ancestors for more information.