edf2csv 0.6.33 → 0.6.35

package/docs/CHANGELOG.md

@@ -3,6 +3,30 @@
 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.35
+
+### Fixed: `EdfFile.sha256()` is public API and the reference never mentioned it
+
+Twenty-two members on that class and this was one of two the page did not name once. It is the
+method `--checksum` runs, and the one with a rule attached that a caller cannot guess: it hashes
+the bytes that were there when the file was opened, through the descriptor already on them, so
+it has to be called before `close()` and it deliberately does not re-read the path.
+
+The test that keeps the reference honest checks the package's top-level exports. `EdfFile` is
+one name; its members are not checked, which is how two of them stayed unwritten.
+
+## 0.6.34
+
+### Fixed: the `NO_SAMPLES` summary repeated a conflation the warning itself stopped making
+
+"No signal file was written because nothing carries any" is the wording for one of two cases.
+The other is a recording holding nothing but EDF+ annotations, which has no channel that could
+have carried anything — and the conversion prints a different sentence for it precisely because
+the first one was, as the source comment puts it, three false statements in one warning when
+applied to that file.
+
+The summary line kept the wording that was split in two.
+
 ## 0.6.33
 
 ### Fixed: the CLI reference's exit codes, the fifth and last page with this gap

package/package.json

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