You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Update release notes for version 2.114.5
Updated release notes to reflect version changes and fixes.
* Add issue reference for DataObjectSearchIndexConf fix
Added GitHub issue reference for DataObjectSearchIndexConf.
* Update release notes with recent fixes and updates
Added fixes for the `project retrieve start` command and updated metadata types support.
* Document new 'RunRelevantTests' flag for deployments
Added information about the new 'RunRelevantTests' flag for deploying metadata, including examples and limitations.
These changes are in the Salesforce CLI release candidate. We plan to include these changes in next week's official release. This list isn't final and is subject to change.
31
31
32
32
------------
33
33
34
+
* NEW: Specify that you want to run only relevant Apex tests when you deploy metadata to your org with the new `RunRelevantTests` value of the `--test-level` flag of the `project deploy start|validate` commands . Examples of relevant tests include:
35
+
36
+
* New or modified tests that are part of the deployment.
37
+
* Specific tests for new or modified Apex classes or triggers that are part of the deployment.
38
+
* Tests that directly or indirectly reference new or modified Apex classes or triggers that are part of the deployment.
39
+
* Tests that are marked critical, which always run.
40
+
41
+
**NOTE**: This feature is available only for Spring '26 orgs (API version 66.0).
42
+
43
+
This example deploys source files in the `force-app` package directory to the org with alias `my-scratch` and runs only the Apex tests that are relevant to the actual metadata that's being deployed:
44
+
45
+
```bash
46
+
sf project deploy start --source-dir force-app --test-level RunRelevantTests --target-org my-scratch
* FIX: The `project retrieve start` command now correctly fails and outputs an error message if you specify an output directory (with the `--output-dir` flag) that is outside of the Salesforce DX project. (GitHub Issue [#3432](https://github.com/forcedotcom/cli/issues/3432), plugin-deploy-retrieve PR [#1480](https://github.com/salesforcecli/plugin-deploy-retrieve/pull/1480))
51
+
52
+
* FIX: Salesforce DX projects now support these [metadata types](https://github.com/forcedotcom/source-deploy-retrieve/blob/main/src/registry/metadataRegistry.json):
0 commit comments