edf2csv 0.6.7 → 0.6.9

package/docs/CHANGELOG.md

@@ -3,6 +3,28 @@
 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.9
+
+### Fixed: package-lock.json had been claiming 0.5.51 for fifty-eight releases
+
+The lockfile carries the package's version in two places and both had stopped moving. Nothing
+breaks on it — `npm ci` does not read the field, and `npm install` rewrites it — but anyone
+checking out a tag and opening the file is told a version other than the one they checked out.
+
+CITATION.cff had exactly this happen, 107 releases of it, and the answer was a test asserting
+it against `package.json`. That test now checks the lockfile in the same breath.
+
+## 0.6.8
+
+### Fixed: the `--info` table's `OUTPUT` column has three values and the reference listed two
+
+`(no samples)` has been printed since 0.4.53, for a channel that declares zero samples per data
+record, and the page enumerating the column said only "the file the channel would land in, or
+`(not selected)` when `--channels` excludes it". A reader meeting the third value had nowhere
+to look it up, and the obvious guess — that it means the same as `(not selected)` — is the one
+0.4.53 exists to contradict: a channel asked for by name and carrying nothing is not a channel
+that went unasked for.
+
 ## 0.6.7
 
 ### Fixed: `--info` and `--info --json` listed the same warnings in different orders

package/package.json

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