edfcore 0.6.123 → 0.6.125

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.123";
+export declare const VERSION = "0.6.125";
 //# 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.123';
+export const VERSION = '0.6.125';
 //# sourceMappingURL=constants.js.map

package/docs/CHANGELOG.md

@@ -6,6 +6,25 @@ 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.125
+
+- **Documented** the `maxItems` rule 0.6.115 changed, in all three tables that carry the option.
+- `api-primitives.md` listed four behaviours for it and `api-helpers.md` listed none; neither said
+  what happens to a value that is not a number, which until 0.6.115 was "it is coerced". A rule
+  stated in one table of three is a rule two readers never meet, so the check asserts every
+  `maxItems` row on both pages states it.
+- The fractional-limit behaviour, which was true all along and written down nowhere, is stated too.
+
+## 0.6.124
+
+- **Documented** when `streamRecords` checks its arguments, which 0.6.118 changed and the page did
+  not say.
+- `api-helpers.md` described the narrower rule it had — "`signalIndices` is validated before the
+  window is resolved" — and left the reader to assume the rest arrives with the data. Every argument
+  is now checked by the call rather than by the first turn of the loop, and the page says so, with
+  the reason: a pipeline that builds the stream in one function and consumes it in another used to
+  get the refusal in the second, and a stream built and then dropped never reported it at all.
+
 ## 0.6.123
 
 - **Fixed** `resolveTimeWindow` mapping a window onto a discontinuous file when handed the header

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.6.123",
+  "version": "0.6.125",
   "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.123';
+export const VERSION = '0.6.125';