apextestlist 1.15.0 → 1.15.2

package/CHANGELOG.md

@@ -5,6 +5,20 @@
 
 All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
 
+## [1.15.2](https://github.com/wisefoxme/apex-test-list/compare/v1.15.1...v1.15.2) (2026-10-11)
+
+
+### Bug Fixes
+
+* **deps:** bump the dependencies group across 1 directory with 3 updates ([#431](https://github.com/wisefoxme/apex-test-list/issues/431)) ([4c7be64](https://github.com/wisefoxme/apex-test-list/commit/4c7be64a38446d8e8391fcaab1b7b50a184c28d7))
+
+## [1.15.1](https://github.com/wisefoxme/apex-test-list/compare/v1.15.0...v1.15.1) (2026-09-28)
+
+
+### Bug Fixes
+
+* **deps:** bump @salesforce/core in the dependencies group ([#426](https://github.com/wisefoxme/apex-test-list/issues/426)) ([f98d484](https://github.com/wisefoxme/apex-test-list/commit/f98d48450fa7d2f54e8b6ec8cb075c5709e39144))
+
 ## [1.15.0](https://github.com/wisefoxme/apex-test-list/compare/v1.14.4...v1.15.0) (2026-09-16)
 
 

package/README.md

@@ -20,6 +20,7 @@ A plugin that generates a list of tests that your automated process should run,
   - [3. `@isTest` (Apex Annotation)](#3-istest-apex-annotation)
   - [4. `.test-dependencies.yml` (Centralized Metadata Filter)](#4-test-dependenciesyml-centralized-metadata-filter)
 - [Running the Tool](#running-the-tool)
+  - [Explicit Test Level for Deploy and Validate](#explicit-test-level-for-deploy-and-validate)
   - [Handling Missing Tests](#handling-missing-tests)
   - [Handling Missing Annotations](#handling-missing-annotations)
   - [Failing When No Tests Are Found](#failing-when-no-tests-are-found)
@@ -124,13 +125,29 @@ Example output:
 This command is useful in CI/CD pipelines, dynamically generating the test list for deployments:
 
 ```sh
-sf project deploy start $(sf apextests list)
+sf project deploy start --test-level RunSpecifiedTests $(sf apextests list)
 ```
 
 The final deployment command would look like:
 
 ```sh
-sf project deploy start --tests SampleTest SuperSampleTest Sample2Test SuperSample2Test SampleTriggerTest
+sf project deploy start --test-level RunSpecifiedTests --tests SampleTest SuperSampleTest Sample2Test SuperSample2Test SampleTriggerTest
+```
+
+### Explicit Test Level for Deploy and Validate
+
+When you append `sf apextests list` output (or the GitHub Action `command` output) to `sf project deploy start` or `sf project deploy validate`, explicitly pass `--test-level RunSpecifiedTests`. Without it, the deploy or validation can fail immediately with:
+
+```text
+Error (1): INVALID_OPERATION: runTests can only be used with a testLevel of RunSpecifiedTests
+```
+
+Salesforce CLI documentation suggests that providing `--tests` should infer `RunSpecifiedTests`, but behavior differs between deploy subcommands. In practice, `sf project deploy validate` does not set the level implicitly (a fix is tracked in [salesforcecli/plugin-deploy-retrieve#1650](https://github.com/salesforcecli/plugin-deploy-retrieve/pull/1650)). Using an explicit test level works for both start and validate.
+
+With a manifest:
+
+```sh
+sf project deploy start -x package/package.xml --test-level RunSpecifiedTests $(sf apextests list -x package/package.xml)
 ```
 
 If no test methods are found, the command output will be empty and will present this warning:
@@ -198,7 +215,7 @@ For GitHub Actions, this is also available as a native Action — no `sf` CLI or
     ignore-missing-tests: 'true'
 
 - name: Deploy with the specified tests
-  run: sf project deploy start -x package.xml ${{ steps.list.outputs.command }}
+  run: sf project deploy start -x package.xml --test-level RunSpecifiedTests ${{ steps.list.outputs.command }}
 ```
 
 ### Inputs

package/oclif.manifest.json

@@ -119,5 +119,5 @@
       ]
     }
   },
-  "version": "1.15.0"
+  "version": "1.15.2"
 }

package/package.json

@@ -1,32 +1,32 @@
 {
   "name": "apextestlist",
   "description": "A plugin that generates a list of apex test and test suite names for use in CI/CD pipelines.",
-  "version": "1.15.0",
+  "version": "1.15.2",
   "dependencies": {
-    "@oclif/core": "5.0.0",
-    "@salesforce/core": "9.1.11",
-    "@salesforce/sf-plugins-core": "13.0.4"
+    "@oclif/core": "5.1.2",
+    "@salesforce/core": "9.3.2",
+    "@salesforce/sf-plugins-core": "13.0.5"
   },
   "devDependencies": {
     "@actions/core": "3.0.1",
-    "@biomejs/biome": "2.5.12",
-    "@commitlint/cli": "21.2.2",
-    "@commitlint/config-conventional": "21.2.2",
-    "@salesforce/cli-plugins-testkit": "5.3.66",
+    "@biomejs/biome": "2.5.15",
+    "@commitlint/cli": "21.2.3",
+    "@commitlint/config-conventional": "21.2.3",
+    "@salesforce/cli-plugins-testkit": "5.3.68",
     "@salesforce/dev-config": "4.3.3",
     "@stryker-mutator/core": "10.0.0",
     "@stryker-mutator/vitest-runner": "10.0.0",
-    "@types/node": "26.5.1",
-    "@vitest/coverage-v8": "5.0.0",
+    "@types/node": "26.6.4",
+    "@vitest/coverage-v8": "5.0.3",
     "esbuild": "0.28.2",
     "husky": "9.1.7",
-    "knip": "6.35.1",
-    "lint-staged": "17.5.0",
+    "knip": "6.40.0",
+    "lint-staged": "17.6.0",
     "ls-engines": "0.10.1",
-    "oclif": "5.0.1",
+    "oclif": "6.0.2",
     "shx": "0.4.0",
     "typescript": "7.0.2",
-    "vitest": "5.0.0",
+    "vitest": "5.0.3",
     "wireit": "0.14.13"
   },
   "engines": {