edf2csv 0.6.41 → 0.6.43

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.43
+
+### Fixed: `exceeds_spreadsheet_limit` was emitted by `--info --json` and documented nowhere
+
+Thirty-one snake_case keys are written into the JSON this tool produces — the conversion
+summary, the `--info` document and `metadata.json` — and thirty of them appear somewhere on the
+site. This was the one that did not, on any page, in any form.
+
+It is the machine-readable half of `LARGE_OUTPUT`: a boolean a script can branch on instead of
+matching a warning message, which is exactly what the surrounding paragraphs tell scripts to do.
+Its two siblings in the same object, `rows` and `bytes`, are documented a line away, including
+0.6.0's rule about them being `null` when no signal table is written.
+
+## 0.6.42
+
+### Fixed: the `OUTPUT_UNWRITABLE` list of translated failures, stale since 0.6.11
+
+0.6.11 taught `describeFsError` to say "you are over your disk quota on this filesystem" instead
+of leaking `EDQUOT`, and did not add it to the page enumerating what that function translates.
+The list gave five of its six.
+
+Second time in this line that a message fix has left prose behind it — 0.6.20 was the same shape
+— and both were found by diffing a list against the function it describes rather than by reading
+it. Worth doing after any change to a user-facing string.
+
 ## 0.6.41
 
 ### Fixed: the errno table left out `EPIPE`, the one a shell pipeline produces

package/package.json

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