edf2csv 0.6.36 → 0.6.38

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.38
+
+### Fixed: `INPUT_UNREADABLE` had no section, and is the one that leaves output behind
+
+Second of the four undocumented `ConversionErrorCode` values. It is not a duplicate of
+`UNREADABLE`: that one fails before anything is written, this one fails during the streaming
+pass, so the difference between them is whether there is a half-finished directory on disk. The
+code separates them for exactly that reason — a read failure used to be reported as
+`Writing to "<dir>" failed` with advice about disk space, pointing at the part of the system
+that was working.
+
+The page had the distinction nowhere, so a reader hitting the second met a message whose code
+they could not look up.
+
+## 0.6.37
+
+### Fixed: `INPUT_OUTPUT_COLLISION` had no section on the errors page
+
+All twenty-seven diagnostic codes and all seven fatal reader errors have a section explaining
+cause, behaviour and remedy. Four of the seven `ConversionErrorCode` values do not, and this is
+the first of them — the one that stops a conversion writing a CSV over the recording it is
+reading, which is the least recoverable thing this tool could do and the one place `--force` is
+deliberately powerless.
+
 ## 0.6.36
 
 ### Fixed: `EdfFile.modifiedAtOpenMs` was the last unmentioned member of the class

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edf2csv",
-  "version": "0.6.36",
+  "version": "0.6.38",
   "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",