Salesforce DX Developer Guide
Summer '26 (API version 67.0)
Spring '26 (API version 66.0)
Winter '26 (API version 65.0)
Summer '25 (API version 64.0)
Spring '25 (API version 63.0)
Winter '25 (API version 62.0)
Summer '24 (API version 61.0)
Spring '24 (API version 60.0)
Winter '24 (API version 59.0)
Summer '23 (API version 58.0)
Spring '23 (API version 57.0)
Winter '23 (API version 56.0)
Summer '22 (API version 55.0)
Spring '22 (API version 54.0)
Winter '22 (API version 53.0)
Summer '21 (API version 52.0)
Spring '21 (API version 51.0)
Winter '21 (API version 50.0)
Summer '20 (API version 49.0)
Spring '20 (API version 48.0)
Winter '20 (API version 47.0)
Summer '19 (API version 46.0)
Spring '19 (API version 45.0)
Winter '19 (API version 44.0)
Summer '18 (API version 43.0)
Spring '18 (API version 42.0)
Winter '18 (API version 41.0)
Summer '17 (API version 40.0)
Metadata Coverage
Second-Generation Packaging
What’s a Package?
Workflow for Second-Generation Packages
Project Configuration File for Packages
Keywords
Package Installation Key
Extract Dependency Information from Unlocked Packages
Migrate Deprecated Metadata from Unlocked Packages
Uninstall a Package
Limitations for Salesforce DX
Newer Version Available
Configure Packages
You include an entry in the Salesforce DX project configuration file for each package
to specify its alias, version details, dependencies, features, and org preferences. From
the command line, you can also set or change options, such as specify an installation key,
update the package name, or add a description.
-
Project Configuration File for Packages
The project configuration file is a blueprint for your project and for the outline of a package. The settings in the file determine the package attributes and package contents. -
Keywords
A keyword is a variable that you can use to specify a package version number. -
Package Installation Key
To ensure the security of the metadata in your package, you must specify an installation key when creating a package version. Package creators provide the key to authorized subscribers so they can install the package. Package users provide the key during installation, whether installing the package from the CLI or from a browser. An installation key is required as the first step during installation, ensuring that no package information, like the name and components, is disclosed until the correct installation key is supplied. The installer UI and API changes are effective in the Winter ’18 release. Changes to the Salesforce CLI will be announced in a future release. -
Extract Dependency Information from Unlocked Packages
For an installed unlocked package, you can now run a simple SOQL query to extract its dependency information. You can also create a script to automate the installation of unlocked packages with dependencies.