saffron-ai 0.8.1 → 0.8.3

package/CHANGELOG.md

@@ -4,9 +4,48 @@ All notable changes to Saffron, in one place: the `saffron-ai` runner (npm),
 the VS Code extension (`ChathurangaJayasinghe.saffron-vscode`) and the
 JetBrains plugin (`ai.saffron.jetbrains`). Dates are publish dates.
 
+## 0.8.3
+
+Released 2026-09-22.
+
+Runner
+
+- **A `{unique:...}` or `{data:...}` reference inside a data-table cell is
+  now recorded as the cell reference (`<table:1:email>`), not as the token
+  itself.** The agent types the resolved value, so the recorder matched it
+  against the cell as written and missed. Replay was right either way; the
+  difference is that editing the cell in the feature file now follows the
+  table at zero tokens instead of making the recording stale.
+- Docs: the `model` option says what the default really is (whatever Claude
+  Code currently defaults to, which drifts) and which values it takes, so a
+  project can pin its recording model.
+
+## 0.8.2
+
+Released 2026-09-22.
+
+Runner
+
+- **Split a suite across CI machines: `--shard 2/4` and
+  `saffron report --merge`.** `--workers` stops at one machine's cores;
+  sharding gives the suite to several. Each shard runs a fixed part, split
+  by scenario rather than by file, so one large feature file spreads over
+  every machine, and every scenario runs exactly once. `--shard-by file`
+  (or `"shardBy": "file"`) keeps each feature file on one machine instead,
+  for files whose scenarios share expensive or order-dependent state. A shard writes
+  `.saffron/reports/shard-2-of-4.json` instead of `latest.json` and leaves
+  `history.jsonl` alone, because part of a run would read as a run in the
+  trends. `saffron report --merge` finds the shard reports under `.saffron/`
+  (or the folders you name) and writes `latest.json`, `latest.html` and one
+  history line, with the same totals, scenario order and trends as an
+  unsharded run. It refuses a missing shard, the same shard twice, shards
+  that ran a different suite, and shards from different CI runs; merging
+  twice does not count the run twice. Setup and teardown run on each shard
+  and receive `SAFFRON_SHARD`. The docs have a GitHub Actions example.
+
 ## 0.8.1
 
-Released 2026-09-21.
+Released 2026-09-22.
 
 Runner