edfcore 0.4.307 → 0.4.309

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

package/docs/CHANGELOG.md

@@ -6,6 +6,27 @@ 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.309
+
+- **Added** a check over the fixed header table on `edf-format.md`: ten rows giving the offset and
+  width of every field in the first 256 bytes. The rows are parsed out of the page and compared
+  with `HEADER_FIELDS`, and they also have to tile the block — no gap, no overlap, ending exactly
+  at 256.
+- That page and `physical-values.md` were the only two documentation pages no test named at all.
+  The page is a hand-typed copy of the same table the parser reads, and its whole value is being
+  independent of the library, so an offset corrected in `constants.ts` alone would leave it
+  teaching a byte address that no longer exists.
+
+## 0.4.308
+
+- **Added** the guard for what 0.4.307 fixed: a version another entry calls a hole has to say so in
+  its own entry. The list is derived rather than kept — an entry saying "0.4.287 through 0.4.292
+  were never released" declares six, and each of those six must carry the note itself.
+- Nothing here knows what npm holds, because the suite is offline. Checking the changelog against
+  itself is the strongest form available, and it is the failure that actually happened: fourteen
+  entries written before their release failed, each reading like one that shipped, with the
+  correction sitting in a different entry the reader never reaches.
+
 ## 0.4.307
 
 - **Marked** the fourteen changelog entries for versions that were never released. Each of them —

package/package.json

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