edf2csv 0.6.19 → 0.6.21

package/docs/CHANGELOG.md

@@ -3,6 +3,29 @@
 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.21
+
+### Fixed: getting-started said the output directory is the filename "with `_csv` appended"
+
+That is `recording.edf_csv`. `defaultOutputDir` strips the extension first, so it is
+`recording_csv` — which the same page prints in its own transcript nine lines above, and which
+the other three pages describing this all state correctly as the extension being removed or
+replaced. One page, contradicting itself and the other three, on the first fact anyone learns
+about where their output goes.
+
+## 0.6.20
+
+### Fixed: two pages quoted the short-read error as 0.6.4 stopped printing it
+
+0.6.4 put the count through `counted` so it could not say "1 were available", which added the
+noun: the message now reads `but only 131072 bytes were available`. Two pages quote that error
+verbatim and neither was updated, so this repository spent four versions showing output its own
+tool does not produce — the exact defect most of the 0.5 line was spent removing, introduced by
+a fix for a different one.
+
+Nothing caught it. The suite pins the quoted *hints* and the warnings of one example command;
+these two are error transcripts in prose, which nothing reads.
+
 ## 0.6.19
 
 ### Fixed: "only `--info` output goes to stdout", in the paragraph about piping

package/package.json

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