edfcore 0.4.293 → 0.4.295

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

package/docs/CHANGELOG.md

@@ -6,6 +6,28 @@ 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.295
+
+- **Corrected** the release script's closing message, which 0.4.294 made false one release ago. It
+  said "publish.yml is now running and will publish to npm" and offered `npm view edfcore version`
+  to confirm — advice from when the script exited before the publish began. It now waits for that
+  publish, so by the time those lines print the version is already installable. It says so, and
+  gives the install command and the release URL instead of two ways to check something already
+  known.
+
+## 0.4.294
+
+- **Added** the last wait the release was missing: whether the version actually reached npm. The
+  CI wait from 0.4.244 asks about the commit; `publish.yml` is a different workflow, triggered by
+  the release that was just created, and it runs its own `npm run check` afterwards — so it can
+  fail on something the commit's checks passed, and the script had always exited 0 before it
+  started. That gap cost 0.4.287 through 0.4.292: six versions tagged, six green CI runs, six
+  GitHub releases, and nothing on npm, found only by looking.
+- npm is polled rather than the workflow's status, because the question is whether the version is
+  installable. On timeout it says the tag, release and commit are all correct and the publish is
+  what did not happen, gives the two commands to see why, and warns that re-running the script
+  would cut the next version and leave this one a hole — which is exactly how the six were lost.
+
 ## 0.4.293
 
 - **Moved** the tarball check out of the test suite, which is the only place it could not live.

package/package.json

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