edfcore 0.4.192 → 0.4.194

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

package/docs/CHANGELOG.md

@@ -6,6 +6,22 @@ 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.194
+
+- **Added** the missing `0.2.29` entry. Four numbers have been consumed by a release that failed
+  after bumping, and three say so in this file. 0.2.29 said nothing — while the 0.2.36 entry cites
+  it as the precedent for its own, and `scripts/release.mjs` tells the next person to record a skip
+  "the way 0.2.29, 0.2.36 and 0.2.59 are". Both pointed at the one that was not. Reconstructed from
+  7ea90ff, which carries the 0.2.28 → 0.2.29 bump alongside the lint fix that run died on.
+
+## 0.4.193
+
+- **Added** the guard for 0.4.191 and 0.4.192: both corpus sizes in `tests/README.md` are now
+  measured against the manifest and the `corpus/golden/` directory. Each had gone stale by more
+  than 30% because a file joined a set and the sentence describing it did not, and neither was
+  checkable by reading the sentence. The tolerance is 10%, so a hedged "~" survives a fixture
+  gaining bytes and fails when the set changes.
+
 ## 0.4.192
 
 - **Corrected** the size of the committed parity fixtures, the other stale number in
@@ -4138,6 +4154,14 @@ against the published 0.2.27 tarball rather than assumed.
   refusal for a file whose records really do exist and really are too big, so the guard is still
   covered.
 
+## 0.2.29
+
+Never released. The release run failed `npm run check` on two unused imports in
+`tests/io/hardening.test.ts` after bumping the version, which consumed the number before a tag was
+cut; the scan-buffer fix it was carrying shipped as 0.2.30 instead. Written down in 0.4.194 — it was
+the only consumed number with no entry of its own, while `0.2.36` above and the guidance in
+`scripts/release.mjs` both name it as one of the recorded ones.
+
 ## 0.2.28
 
 - **Fixed** `readAnnotations` answering on the header's axis for any record range that does not

package/package.json

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