edf2csv 0.6.37 → 0.6.39

package/docs/CHANGELOG.md

@@ -3,6 +3,31 @@
 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.39
+
+### Fixed: `UNSUPPORTED_REQUEST` had no section, and it is the one that exits 2
+
+Third of the four. It is the only `ConversionErrorCode` in `USAGE_ERROR_CODES`, so it is the
+only one where the code a script sees is 2 rather than 1 — a distinction the page's own exit-code
+table draws and this code's absence made unverifiable from the page.
+
+Placed at the head of the usage-error section rather than with the other conversion errors,
+since that is where its exit code puts it.
+
+## 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

package/package.json

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