edfcore 0.4.467 → 0.4.469

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

package/docs/CHANGELOG.md

@@ -6,6 +6,41 @@ 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.4.469
+
+- **Added** the cases where a 206's `Content-Range` cannot be parsed at all. edfcore checks that
+  header against the range it asked for, because `assertExactRead` is a length guard and cannot
+  see a right-sized body taken from the wrong offset — but `rangeFromContentRange` returns
+  `undefined` for anything outside `bytes <first>-<last>/`, and `undefined` means "no usable
+  claim", not "the claim was wrong".
+- Every existing case supplied a well-formed header or none at all, so the two `return undefined`
+  lines in the middle had never run. Turning either into a refusal would reject reads that are
+  fine, from servers that are behaving within RFC 7233.
+- Four shapes reach them and all four occur: a range unit that is not `bytes`, the unsatisfiable
+  `bytes */total` form, a header truncated before the total, and byte positions past 2^53 from a
+  proxy in front of an object store that counts in something else. A `FetchLike` double answering
+  every header with `null` is the fifth, and is the reason the rule is written this way.
+- The non-vacuous half is asserted on both sides of them: a header that DOES parse and names a
+  different part of the resource is still refused, and a short body behind an unreadable header is
+  still caught by length. "Unreadable" has not become "unchecked".
+
+## 0.4.468
+
+- **Added** tests for the half of `redactDiagnostic` that had never been asked: what happens to a
+  diagnostic on a withheld field that carried no `raw` or no `actual`. Both substitutions are
+  conditional, and making either unconditional left the suite green.
+- The consequence is the 0.3.31 failure with its sign flipped. `raw: "[redacted]"` on a diagnostic
+  that never held the bytes makes `formatDiagnostics` print a `raw:` line under it, so a reader
+  auditing a report for what the tool held back finds evidence of patient text where there was
+  none. Output that looks redacted is worse than an obvious leak in both directions.
+- Also pinned: `expected` survives redaction. It is the grammar the field should have followed,
+  not a value read out of the file, and substituting it removes the only part of the line that
+  says what to do. And `actual` alone is enough to clear the message, which matters because a
+  diagnostic with no `raw` has no other spelling of the value to substitute by.
+- The diagnostics are written out rather than provoked from a file: `formatDiagnostics` is public
+  and takes any `EdfDiagnostic[]`, every parser-built identification diagnostic happens to carry
+  both fields, and the contract being pinned is the function's rather than one file's.
+
 ## 0.4.467
 
 - **Added** the test for the third arm of `DIGITAL_RANGE_EXCEEDS_FORMAT`'s advice clause, added in

package/package.json

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