@qawolf/cli 1.19.1 → 1.20.0

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.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@qawolf/cli",
3
- "version": "1.19.1",
3
+ "version": "1.20.0",
4
4
  "description": "Run and manage QA Wolf flows from the terminal, CI, or an AI agent",
5
5
  "keywords": [
6
6
  "automation",
@@ -17,7 +17,7 @@ Commands that target a runner find one in this order: `--runner`, then
17
17
  `QAWOLF_RUNNER_ID`, then the runner stored for the current directory (which
18
18
  `qawolf runner launch` sets). Setting the environment variable once is the most
19
19
  robust for a harness whose working directory may not be stable, but it comes
20
- with two catches worth knowing before you rely on it.
20
+ with three catches worth knowing before you rely on it.
21
21
 
22
22
  `qawolf runner launch` is not in that order: it takes its id from `--id` and
23
23
  never reads `QAWOLF_RUNNER_ID`. Bare `qawolf runner launch` invents a random id,
@@ -31,6 +31,13 @@ auto-launch described next: instead of starting `agent-1`, commands try to reach
31
31
  it and fail with exit code `4`, which reads as "retry" and never succeeds.
32
32
  Launch that id once yourself and the rest follows.
33
33
 
34
+ And launching an id that differs from `QAWOLF_RUNNER_ID` prints a warning on
35
+ stderr naming both ids: the variable still outranks the directory default, so
36
+ commands that omit `--runner` keep going to whatever it names, not the runner
37
+ you just launched. Expected when you are launching an additional runner on
38
+ purpose — address that one with `--runner` rather than re-exporting the
39
+ variable, which would repoint every other runner-less command too.
40
+
34
41
  If nothing names a runner, the commands that change something will launch one
35
42
  and say so on stderr, naming it: `run`, `act` and `exec`. **Read that
36
43
  announcement.** The browser it just started is fresh: nothing has been run on it,