edf2csv 0.6.48 → 0.6.50

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.50
+
+### Fixed: the third page defining an empty `duration_s` as "no duration"
+
+0.6.22 fixed this on the annotations page. `output-files.md` has had it right all along. This is
+the third copy, in the file-summary at the top of recipes, and it is the same half-definition:
+an empty cell also means the file stated a duration that could not be read, which is why
+`ANNOTATION_DECODE_FAILED` counts those rows and says so.
+
+Three pages, one sentence, written three times — and the two that were wrong were wrong in the
+same direction, because they were describing the behaviour from before the warning existed.
+
+## 0.6.49
+
+### Fixed: recipes showed a 100 Hz row as `286.50000000`
+
+Eight decimal places is what 256 Hz gets. The paragraph is about `signals_100hz.csv`, three code
+blocks under a snippet that loads it, and 100 Hz gets three places — the file really writes
+`286.500`, which converting the page's own example recording confirms.
+
+The point being made is right and worth keeping: a window converted on its own keeps the whole
+recording's clock rather than restarting at zero. It was the illustration that came from a
+different file.
+
 ## 0.6.48
 
 ### Fixed: nothing said the JSON drops the hint every terminal warning carries

package/package.json

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