@vitrinka/cli 3.9.1 → 3.10.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.
Files changed (2) hide show
  1. package/CHANGELOG.md +27 -0
  2. package/package.json +7 -7
package/CHANGELOG.md CHANGED
@@ -3,6 +3,33 @@
3
3
  `vitrinka update` prints the sections newer than your previous version after
4
4
  updating — keep entries short and user-facing.
5
5
 
6
+ ## 3.10.0
7
+
8
+ One verb per testing lane: run your suite, or explore by hand, and vitrinka
9
+ keeps the QA record — task, journeys, verdicts, board, screenshots, bugs.
10
+
11
+ ### Added
12
+ - **`vitrinka run -- <test command>`** — runs the command with the run env set
13
+ (`VITRINKA_RUN_ID`, `VITRINKA_RUN_DIR`, `VITRINKA_RUN_STARTED_AT`,
14
+ `VITRINKA_SHOTS=always`), finds the results it left (JUnit XML, a Playwright
15
+ JSON report, `allure-results/`, wdio reports or a run manifest; declared
16
+ runners first, else a scan since the start) and publishes them. Exits with
17
+ the command's exit code; `--dry-run` prints the folded manifest.
18
+ - **`vitrinka usertest start · case · verdict · finish`** — an exploratory
19
+ session over `snap`: every capture attaches to the open case, `finish`
20
+ publishes one journey per case with its verdict and shots.
21
+ - **`vitrinka project setup --runners [--check]`** — declares where each
22
+ detected runner (Playwright · wdio · Jest · Vitest) writes results in
23
+ `.vitrinka/project.json`; `--check` exits 1 on drift.
24
+ - A run with no task in context lands under the project's rolling
25
+ **Unplanned runs** epic instead of failing; `run publish` does the same.
26
+ - The run door accepts JUnit XML and Playwright JSON bodies directly
27
+ (`POST /tasks/{id}/run`, `POST /projects/{project}/run`).
28
+
29
+ ### Changed
30
+ - The `usertest` skill is the two verbs; board mechanics left it. The
31
+ publisher agent keeps only walkthrough boards.
32
+
6
33
  ## 3.9.1
7
34
 
8
35
  The feature-lifecycle follow-ups: the QA board and final artifact from the
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@vitrinka/cli",
3
- "version": "3.9.1",
3
+ "version": "3.10.0",
4
4
  "description": "vitrinka CLI — capture and publish artifact sets, drive the annotation-board work queue. Thin npm launcher for the single-binary Go CLI.",
5
5
  "bin": {
6
6
  "vitrinka": "bin/vitrinka.js"
@@ -15,12 +15,12 @@
15
15
  "node": ">=18"
16
16
  },
17
17
  "optionalDependencies": {
18
- "@vitrinka/cli-darwin-arm64": "3.9.1",
19
- "@vitrinka/cli-darwin-x64": "3.9.1",
20
- "@vitrinka/cli-linux-arm64": "3.9.1",
21
- "@vitrinka/cli-linux-x64": "3.9.1",
22
- "@vitrinka/cli-win32-arm64": "3.9.1",
23
- "@vitrinka/cli-win32-x64": "3.9.1"
18
+ "@vitrinka/cli-darwin-arm64": "3.10.0",
19
+ "@vitrinka/cli-darwin-x64": "3.10.0",
20
+ "@vitrinka/cli-linux-arm64": "3.10.0",
21
+ "@vitrinka/cli-linux-x64": "3.10.0",
22
+ "@vitrinka/cli-win32-arm64": "3.10.0",
23
+ "@vitrinka/cli-win32-x64": "3.10.0"
24
24
  },
25
25
  "keywords": [
26
26
  "vitrinka",