Salesforce DX Developer Guide

How Salesforce Developer Experience Changes the Way You Work
Project Setup
Authorization
Scratch Orgs
Development
Build and Release Your App
Develop Second-Generation Packages (Beta)
Second-Generation Packaging
Types of Packaging Projects
Before You Create Second-Generation Packages
Workflow for Second-Generation Packages
Plan Second-Generation Packages
Configure Packages in the sfdx-project.json File
Features
Package Versions
Keywords
Package Dependencies
Package Ancestors
Package Installation Key
Create a Package
Install a Package
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

Package Versions

Specify the package versions in the sfdx-project.json file.
Note these considerations for package versions.
  • Version numbers are formatted as major.minor.patch.build. For example, 1.2.0.8.

    During the beta, the patch number must be 0, because patches aren’t yet supported.

    Note

  • A subscriber can upgrade a managed package only if the upgrade has an ancestor that was previously installed in the subscriber org. Remember that when you create a managed package version, you specify the ancestorId or ancestorVersion in sfdx-project.json. As long as the ancestor is specified when you create a managed package version, you can easily support upgrades.