edf2csv 0.6.17 → 0.6.19

package/docs/CHANGELOG.md

@@ -3,6 +3,26 @@
 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.19
+
+### Fixed: "only `--info` output goes to stdout", in the paragraph about piping
+
+The sentence exists to say a conversion is safe to pipe, and the flag it leaves out is the one
+that puts a CSV on the pipe. `--stdout` is the whole reason someone reads this paragraph before
+writing `edf2csv rec.edf --stdout | head`. Same omission 0.6.17 fixed in getting-started's
+version of the claim, which at least named `--help` and `--version`.
+
+## 0.6.18
+
+### Fixed: the FAQ's exit codes, in the answer written for scripts
+
+Third page with this gap, after the README in 0.6.10 and getting-started in 0.6.16, and the one
+where it costs most: the question is "how do I check whether a conversion had problems from a
+script", and the answer gave three codes as the whole set. A pipeline built on it reads 1 as "a
+problem with the file or the output directory" — but the same page recommends `--strict` two
+sections later, and `--strict` returns 1 over a conversion that wrote every file it meant to.
+130 was missing as well.
+
 ## 0.6.17
 
 ### Fixed: the list of what writes to stdout left out `--stdout`

package/package.json

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