edf2csv 0.6.47 → 0.6.49

package/docs/CHANGELOG.md

@@ -3,6 +3,31 @@
 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.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
+
+A warning on screen is two lines: the message, and an indented hint saying what to do. The
+`warnings` array and `metadata.json`'s `notes` carry `code`, `severity` and `message` — and every
+transcript on the site shows both lines, so a reader moving from the terminal to a script has no
+reason to expect the second one to be gone.
+
+Nothing on any page was false about this; it was absent, which for a machine-readable contract
+is the same problem. Said outright now, with the reason — a hint varies with the run while a
+code does not — and a pointer to where the remedy lives.
+
 ## 0.6.47
 
 ### Fixed: `INPUT_CHANGED` missing from the list of warnings `--info` cannot raise

package/package.json

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