@salesforce/plugin-deploy-retrieve 3.24.2 → 3.24.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (53) hide show
  1. package/LICENSE.txt +1 -1
  2. package/README.md +53 -23
  3. package/lib/commands/project/convert/mdapi.js +1 -1
  4. package/lib/commands/project/convert/source-behavior.js +1 -1
  5. package/lib/commands/project/convert/source.js +1 -1
  6. package/lib/commands/project/delete/source.js +1 -1
  7. package/lib/commands/project/delete/tracking.js +1 -1
  8. package/lib/commands/project/deploy/cancel.js +1 -1
  9. package/lib/commands/project/deploy/preview.js +1 -1
  10. package/lib/commands/project/deploy/quick.js +1 -1
  11. package/lib/commands/project/deploy/report.js +1 -1
  12. package/lib/commands/project/deploy/resume.js +1 -1
  13. package/lib/commands/project/deploy/start.js +1 -1
  14. package/lib/commands/project/deploy/validate.js +1 -1
  15. package/lib/commands/project/generate/manifest.js +1 -1
  16. package/lib/commands/project/list/ignored.js +1 -1
  17. package/lib/commands/project/reset/tracking.js +1 -1
  18. package/lib/commands/project/retrieve/preview.js +1 -1
  19. package/lib/commands/project/retrieve/start.js +1 -1
  20. package/lib/configMeta.js +1 -1
  21. package/lib/formatters/asyncDeployCancelResultFormatter.js +1 -1
  22. package/lib/formatters/asyncDeployResultFormatter.js +1 -1
  23. package/lib/formatters/deleteResultFormatter.js +1 -1
  24. package/lib/formatters/deployCancelResultFormatter.js +1 -1
  25. package/lib/formatters/deployReportResultFormatter.js +1 -1
  26. package/lib/formatters/deployResultFormatter.js +1 -1
  27. package/lib/formatters/metadataConvertResultFormatter.js +1 -1
  28. package/lib/formatters/metadataRetrieveResultFormatter.js +1 -1
  29. package/lib/formatters/retrieveResultFormatter.js +1 -1
  30. package/lib/formatters/sourceConvertResultFormatter.js +1 -1
  31. package/lib/formatters/testResultsFormatter.js +1 -1
  32. package/lib/hooks/diagnostics.js +1 -1
  33. package/lib/index.js +1 -1
  34. package/lib/utils/conflicts.js +1 -1
  35. package/lib/utils/convertBehavior.js +1 -1
  36. package/lib/utils/coverage.js +1 -1
  37. package/lib/utils/deploy.js +1 -1
  38. package/lib/utils/deployCache.js +1 -1
  39. package/lib/utils/deployStages.js +1 -1
  40. package/lib/utils/errorCodes.js +1 -1
  41. package/lib/utils/flags.js +1 -1
  42. package/lib/utils/manifestCache.js +1 -1
  43. package/lib/utils/metadataTypes.js +1 -1
  44. package/lib/utils/output.js +1 -1
  45. package/lib/utils/previewOutput.js +1 -1
  46. package/lib/utils/project.js +1 -1
  47. package/lib/utils/promiseQueue.js +1 -1
  48. package/lib/utils/types.js +1 -1
  49. package/messages/delete.source.md +3 -1
  50. package/messages/deploy.metadata.md +2 -2
  51. package/messages/deploy.metadata.validate.md +3 -1
  52. package/oclif.manifest.json +1044 -1044
  53. package/package.json +5 -5
package/messages/deploy.metadata.md CHANGED
@@ -104,9 +104,9 @@ Valid values are:
104
104
 
105
105
  - RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.
106
106
 
107
- - RunRelevantTests — Runs only tests that are relevant to the files being deployed.
107
+ - RunRelevantTests (Beta) — Runs only tests that are relevant to the files being deployed. Salesforce automatically identifies the relevant tests based on an analysis of the deployment payload and the payload dependencies. For fine-grained control, you can also annotate test classes so that they always run in certain conditions. See "@IsTest Annotation" in the "Apex Developer Guide" (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_isTest.htm). Each class and trigger in the deployment package must be covered by the executed tests for a minimum of 75% code coverage. This coverage is computed for each class and triggers individually and is different than the overall coverage percentage.
108
108
 
109
- If you don’t specify a test level, the default behavior depends on the contents of your deployment package and target org. For more information, see [Running Tests in a Deployment](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm) in the "Metadata API Developer Guide".
109
+ If you don’t specify a test level, the default behavior depends on the contents of your deployment package and target org. For more information, see "Running Tests in a Deployment" (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm) in the "Metadata API Developer Guide".
110
110
 
111
111
  # flags.source-dir.summary
112
112
 
package/messages/deploy.metadata.validate.md CHANGED
@@ -52,7 +52,9 @@ Valid values are:
52
52
 
53
53
  - RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.
54
54
 
55
- - RunRelevantTests — Runs only tests that are relevant to the files being deployed.
55
+ - RunRelevantTests (Beta) — Runs only tests that are relevant to the files being deployed. Salesforce automatically identifies the relevant tests based on an analysis of the deployment payload and the payload dependencies. For fine-grained control, you can also annotate test classes so that they always run in certain conditions. See "@IsTest Annotation" in the "Apex Developer Guide" (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_isTest.htm). Each class and trigger in the deployment package must be covered by the executed tests for a minimum of 75% code coverage. This coverage is computed for each class and triggers individually and is different than the overall coverage percentage.
56
+
57
+ If you don’t specify a test level, the default behavior depends on the contents of your deployment package and target org. For more information, see "Running Tests in a Deployment" (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm) in the "Metadata API Developer Guide".
56
58
 
57
59
  # flags.source-dir.summary
58
60