Name the version in every seed promise, and say to regenerate seeded fixtures when it changes

2026-10-04 17:11:27 +02:00
parent 0bedcd47e2
commit 6eb9880a3f
4 changed files with 12 additions and 9 deletions
@@ -829,8 +829,9 @@ the output.

 Semver tags on `main`, `v0.1.0` first; one version covers the shipped data, the
 library and the CLI, and [`CHANGELOG.md`](CHANGELOG.md) names what each release
-changed. A consumer's data, code and scripts keep working across a minor or a patch:
-a minor only adds, and a major is the only release that changes what exists.
+changed. A consumer's data, code and scripts keep working across a minor or a patch,
+except output pinned to a seed. A minor only adds, and a major is the only release that
+changes what exists.

 | Surface | Major | Minor |
 |---------|-------|-------|
@@ -843,9 +844,11 @@ a minor only adds, and a major is the only release that changes what exists.
 A patch changes no row of this table: performance, docs, or a fix inside a promised
 behaviour that adds or removes no value and changes no path, format or spelling.

-Any release, a patch too, may change what a seed draws, so pin seeded fixtures to one
-version. An error's wording may
-improve in a minor; the path, rejected spelling and replacement it names may not.
+Any release, a patch too, may change what a seed draws, so regenerate seeded fixtures
+whenever the fejkdata version changes.
+
+An error's wording may improve in a minor; the path, rejected spelling and replacement
+it names may not.

 Before `v1.0.0` a minor is the breaking unit: `0.(x+1).0` may carry a major's
 changes, each named in the changelog, and a `0.x.y` patch may not. `v1.0.0` is