edfcore 0.4.243 → 0.4.245

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

package/docs/CHANGELOG.md

@@ -6,6 +6,31 @@ 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.245
+
+- **Corrected** the note in `scripts/release.mjs` that tells you how to audit changelog headings
+  against the tags. It says to compare `git show <tag>:docs/CHANGELOG.md`, which is how the 0.2.29
+  and 0.2.36 drift was found, and that stopped being true for part of the history: 0.4.150 through
+  0.4.244 were squashed into 43 commits, so 51 of those tags now share a commit with a later
+  version and hand back that version's changelog. Tags before 0.4.150 are unaffected, and the
+  original commits are on the `archive/pre-squash-2026-08-16` branch. The note says so, and says
+  why the check itself is unaffected: it runs before the commit, so it never depended on the
+  history being reconstructible afterwards.
+
+## 0.4.244
+
+- **Added** a wait for CI before the GitHub release is created, which is what stops a green local
+  run from becoming a version that never reaches npm. `npm run check` runs on the machine cutting
+  the tag, and that is not the same question as whether it passes: twice this week a check was
+  green here and red on every runner — one read a file whose tsconfig lives in
+  `website/node_modules`, which CI does not install, and one required the gitignored
+  `tests/scratch/` to exist. Between them 0.4.231–0.4.236 and 0.4.241–0.4.242 were tagged and
+  never published, eight numbers refused by `publish.yml` long after this script had exited 0.
+  The script now polls the check runs for the exact commit it pushed and refuses to open the door
+  to npm if any of them fails. That turns a silent hole into a stop with the tag intact and the
+  version still recoverable by `gh release create` — the same recovery 0.4.226 wrote the message
+  for. It gives up after twenty minutes and says so rather than hanging.
+
 ## 0.4.243
 
 - **Fixed** the layout-table check added in 0.4.241, which compared `tests/README.md` against the

package/package.json

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