Salesforce DX Developer Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
How Salesforce Developer Experience (DX) Tooling Changes the Way You Work
Provide Developers Access to Salesforce DX Tools
Project Setup
Authorization
Metadata Coverage
Scratch Orgs
Sandboxes
Track Changes Between Your Project and Org
Work with Data
Development
Build and Release Your App
Unlocked Packages
What’s an Unlocked Package?
Package-Based Development Model
Before You Create Unlocked Packages
Know Your Orgs
Create Org-Dependent Unlocked Packages
Workflow for Unlocked Packages
Configure Unlocked Packages
How We Handle Profile Settings in Unlocked Packages
Develop Unlocked Packages
Create and Update an Unlocked Package
Create New Versions of an Unlocked Package
Simplify Unlocked Package Development by Creating and Specifying an Org Shape
Use Branches in Unlocked Packaging
Target a Specific Release for Your Unlocked Packages During Salesforce Release Transitions
Guidance for Package Version Numbering
Code Coverage for Unlocked Packages
Considerations for Promoting Packages with Dependencies
Release an Unlocked Package
Update an Unlocked Package Version
Hard-Deleted Components in Unlocked Packages
Delete an Unlocked Package or Package Version
View Package Details
Push a Package Upgrade for Unlocked Packages
Install an Unlocked Package
Migrate Deprecated Metadata from Unlocked Packages
Uninstall an Unlocked Package
Transfer an Unlocked Package to a Different Dev Hub
Continuous Integration
Troubleshoot Salesforce DX
Limitations for Salesforce DX
PDF

Target a Specific Release for Your Unlocked Packages During Salesforce Release Transitions

During major Salesforce release transitions, you can specify preview or previous when creating a package version. Specifying the release version for a package allows you to test upcoming features, run regression tests, and support customers regardless of which Salesforce release their org is on. Previously, you could only create package versions that matched the Salesforce release your Dev Hub org was on.
To create a package version based on a preview or previous Salesforce release version, create a scratch org definition file that includes either:
{
    "release": "previous"
}
or 
{
    "release": "preview"
}

In the sfdx-project.json file, set the sourceApiVersion to correspond with the release version of the package version you’re creating. If you are targeting a previous release, any sourceApiVersion value below the current release is accepted.

Then when you create your package version, specify the scratch org definition file.
sf package version create --package pkgA --definition-file config/project-scratch-def.json

Preview start date is when sandbox instances are upgraded. Preview end date is when all instances are on the GA release.

Release Version Preview Start Date Preview End Date
Summer ’25 May 11, 2025 June 14, 2025
Winter ’26 September 7, 2025 October 11, 2025
Spring ’26 January 11, 2026 February 21, 2026