edfcore 0.3.86 → 0.3.88

package/CHANGELOG.md

@@ -6,6 +6,36 @@ 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.3.88
+
+- **Fixed** `data-sources.md` saying the ignored-`Range` check "happens during the length probe,
+  before a second request is made". The probe runs on only one of the three ways `httpSource` learns
+  a length, and on the other two the check cannot fire until the caller's first `read()`.
+  - `httpSource` returns before the probe when `options.byteLength` was supplied, and again when
+    `HEAD` gave a usable `Content-Length`. A CDN that answers `HEAD` and then ignores `Range` — the
+    ordinary shape of this failure — therefore hands back a source that constructs cleanly and
+    refuses the first read. A reader who trusted the page treated a successful `httpSource()` as
+    proof the origin honours `Range`.
+  - The page now gives the rule as a table of the three paths and says which of them can see a 200
+    at construction.
+- The test drives both branches through a fake `fetch` and asserts the request METHODS issued —
+  `['HEAD']` when HEAD answers, `['HEAD', 'GET']` when it does not — so it pins the reason the two
+  behave differently, not just that they do.
+
+## 0.3.87
+
+- **Fixed** `api-validate.md` saying "The other five are also emitted by the parser" under a
+  ten-row table from which four codes had just been excluded. Ten minus four is six, and all six
+  really are parser codes: `RECORD_SIZE_ABOVE_RECOMMENDED`, `PATIENT_ID_NONCONFORMANT`,
+  `RECORDING_ID_NONCONFORMANT`, `DATE_UNPARSEABLE`, `DATE_FIELDS_DISAGREE` and
+  `STARTTIME_UNPARSEABLE`.
+- The sentence is load-bearing — it is how a reader knows the report stands on its own rather than
+  only making sense beside `header.diagnostics` — so a reader who counted the table and got a
+  different answer had reason to doubt the claim rather than the arithmetic.
+- Both numbers are now derived from the table itself: the count of rows, minus the count the prose
+  says exist nowhere else. Adding a row fails the suite until the prose is updated, which is the
+  rule 0.3.63 applied to `diagnostics.md` after the same kind of drift.
+
 ## 0.3.86
 
 - **Fixed** `formatStartTimeNaive`'s reference entry naming one of its two `undefined` cases, and

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

package/package.json

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