saffron-ai 0.8.1 → 0.8.2

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/CHANGELOG.md CHANGED
@@ -4,9 +4,32 @@ All notable changes to Saffron, in one place: the `saffron-ai` runner (npm),
4
4
  the VS Code extension (`ChathurangaJayasinghe.saffron-vscode`) and the
5
5
  JetBrains plugin (`ai.saffron.jetbrains`). Dates are publish dates.
6
6
 
7
+ ## 0.8.2
8
+
9
+ Released 2026-09-22.
10
+
11
+ Runner
12
+
13
+ - **Split a suite across CI machines: `--shard 2/4` and
14
+ `saffron report --merge`.** `--workers` stops at one machine's cores;
15
+ sharding gives the suite to several. Each shard runs a fixed part, split
16
+ by scenario rather than by file, so one large feature file spreads over
17
+ every machine, and every scenario runs exactly once. `--shard-by file`
18
+ (or `"shardBy": "file"`) keeps each feature file on one machine instead,
19
+ for files whose scenarios share expensive or order-dependent state. A shard writes
20
+ `.saffron/reports/shard-2-of-4.json` instead of `latest.json` and leaves
21
+ `history.jsonl` alone, because part of a run would read as a run in the
22
+ trends. `saffron report --merge` finds the shard reports under `.saffron/`
23
+ (or the folders you name) and writes `latest.json`, `latest.html` and one
24
+ history line, with the same totals, scenario order and trends as an
25
+ unsharded run. It refuses a missing shard, the same shard twice, shards
26
+ that ran a different suite, and shards from different CI runs; merging
27
+ twice does not count the run twice. Setup and teardown run on each shard
28
+ and receive `SAFFRON_SHARD`. The docs have a GitHub Actions example.
29
+
7
30
  ## 0.8.1
8
31
 
9
- Released 2026-09-21.
32
+ Released 2026-09-22.
10
33
 
11
34
  Runner
12
35