edfcore 0.6.53 → 0.6.55

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

package/docs/CHANGELOG.md

@@ -6,6 +6,33 @@ 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.55
+
+- **Added** the `redactFields` row to `FormatDiagnosticsOptions` on `api-primitives.md`. The table
+  documented two of the option's three fields, and the missing one is the option whose absence
+  sends a patient's name and birth date to an issue tracker: a diagnostic quotes the raw bytes as
+  written, and for an identification field those bytes are a person.
+- It was documented elsewhere — `api-helpers.md` names it, the CLI passes it, `cli.md` explains
+  why — but the reference table for the function did not have it, which is the page a caller
+  building their own report reads.
+- A test now compares EVERY `| \`Interface\` | Type |` table on the site against the interface it
+  names, in both directions. That is the third instance of one class in three releases —
+  `EdfLocation` lost its two `*Ticks` in 0.6.53, `EdfChunkSignal` lost `startTicks` in 0.6.54 —
+  and all three were found by reading rather than by anything that runs. A field added to a shape
+  in `src/` now fails here until its row exists.
+
+## 0.6.54
+
+- **Fixed** the `EdfChunkSignal` table on `reading-signals.md`, which listed six of the shape's
+  seven fields and dropped `startTicks`.
+- That is the field the rest of the package points at. `trimToWindow` measures its window from
+  it, every read puts its chunks on the same tick axis, and `api-types.md` spends a paragraph on
+  why the `startSeconds` beside it can be a sub-tick out after a trim. The guide a reader follows
+  to get their first chunk showed them the float64 half and did not say the exact one existed.
+- Same shape as 0.6.53, one page over. The test reads the fields off a chunk a real read returned
+  and compares the table with that, so it fails on a field added to the type as well as on one
+  dropped from the page.
+
 ## 0.6.53
 
 - **Fixed** the `EdfLocation` table on `api-types.md`, which listed three of the shape's five

package/package.json

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