edfcore 0.6.50 → 0.6.52

package/README.md

@@ -21,7 +21,7 @@ npx edfcore validate overnight.edf        # full conformance sweep; exits 1 on f
 npx edfcore json overnight.edf            # the header as JSON, for jq
 ```
 
-Patient identification is omitted unless you pass `--patient`. Diagnostics and events print twenty
+Patient identification is omitted unless you pass `--patient`. Diagnostics, events and gaps print twenty
 at a time; `--limit <n>` changes that.
 
 ## How do I read an EDF file in JavaScript?

package/dist/constants.d.ts

@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
     readonly reserved: 224;
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export declare const VERSION = "0.6.50";
+export declare const VERSION = "0.6.52";
 //# sourceMappingURL=constants.d.ts.map

package/dist/constants.js

@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
     reserved: 224,
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.6.50';
+export const VERSION = '0.6.52';
 //# sourceMappingURL=constants.js.map

package/docs/CHANGELOG.md

@@ -6,6 +6,34 @@ alone does not tell you whether you were affected.
 edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
 defect; those are called out below.
 
+## 0.6.52
+
+- **Fixed** the `maxItems` row on `api-primitives.md`, both halves of which described something
+  `formatDiagnostics` does not do.
+- "A non-finite value is ignored" stopped being true in 0.6.1, which made `NaN` a `RangeError`
+  and `-Infinity` show nothing rather than everything. `NaN` is non-finite and it is the value
+  that refusal exists for — `Number()` on an absent environment variable, query parameter or
+  config key — so the page was promising to swallow exactly what the library now refuses, and
+  naming the whole class the release split in two.
+- "`0` shows only the summary line" described a line this function never prints. It renders one
+  block per diagnostic and nothing else, so `maxItems: 0` leaves the `... and N more` notice
+  alone. The summary belongs to `formatValidationReport`, whose own row on `api-helpers.md` says
+  so correctly — which is where the clause appears to have come from.
+- The new test runs the function for each awkward value before reading the page for the claim, so
+  it fails on the behaviour as well as on the wording.
+
+## 0.6.51
+
+- **Fixed** the README's account of what `--limit` caps. It said "Diagnostics and events print
+  twenty at a time", which was true until 0.6.29 brought `gaps` under the same cap. That release
+  updated the usage text and `cli.md` and left the README naming two of the three.
+- `gaps` is the one it mattered for. It is the only listing bounded by nothing but the record
+  count — an ambulatory recorder that stops and restarts across a night produces hundreds of rows
+  — so a reader of the README believed the flag did not reach the command that most needs it.
+- A test now reads the noun list out of the usage text and out of the README and compares them,
+  rather than restating the sentence. `cli-limit-default.test.ts` pins the number; this pins what
+  the number applies to.
+
 ## 0.6.50
 
 - **Changed** the message `--limit -1` earns. It said "`--limit` needs a whole number, received

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.6.50",
+  "version": "0.6.52",
   "description": "Modern, typed, zero-dependency reader for EDF, EDF+, BDF and BDF+ biosignal files. Works in browsers and Node with true random access.",
   "keywords": [
     "edf",

package/src/constants.ts

@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
 } as const;
 
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.6.50';
+export const VERSION = '0.6.52';