edf2csv 0.6.31 → 0.6.33

package/docs/CHANGELOG.md

@@ -3,6 +3,30 @@
 Notable changes to edf2csv. Versions follow [semantic versioning](https://semver.org); while the
 major version is 0, a minor bump may contain breaking changes.
 
+## 0.6.33
+
+### Fixed: the CLI reference's exit codes, the fifth and last page with this gap
+
+"`1` — The file or the destination is the problem" is the sentence the source quotes back at
+itself: `USAGE_ERROR_CODES` in `run.ts` carries it verbatim as the distinction the exit codes
+draw. It is exactly right for every code path except `--strict`, where neither the file nor the
+destination is the problem and the output is written in full.
+
+That completes the sweep — README, getting-started, the FAQ, the warnings page and this one all
+now say the same thing about exit 1, and all five list 130.
+
+## 0.6.32
+
+### Fixed: the canonical exit-code table had the gap the other three pages had
+
+0.6.10, 0.6.16 and 0.6.18 fixed this on the README, getting-started and the FAQ. This is the
+table those pages defer to, and it had the same two omissions: `--strict` returns 1 over a
+conversion that wrote every file it meant to, and Ctrl-C returns 130.
+
+130 is the sharper miss, because the prose directly under the table already discusses it — "a
+signalled child exits 130 or 143" — while explaining how a batch combines codes. The number was
+on the page, in a paragraph about workers, and absent from the list of what the tool returns.
+
 ## 0.6.31
 
 ### Fixed: `ANNOTATION_DECODE_FAILED` also covers a duration that decoded fine

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edf2csv",
-  "version": "0.6.31",
+  "version": "0.6.33",
   "description": "Convert EDF, EDF+ and BDF biosignal recordings (European Data Format) to CSV from the command line. Local, streaming, and never resamples or alters units.",
   "keywords": [
     "edf",