edfcore 0.4.294 → 0.4.296

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

package/docs/CHANGELOG.md

@@ -6,6 +6,26 @@ 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.296
+
+- **Documented** the commands that existed and no page mentioned. 0.4.268 checks that every
+  documented script is real; nothing checked the other direction, and `format`, `release` and the
+  three `verify:*` scripts had accumulated unmentioned. A contributor-facing script nobody
+  documents is a script nobody runs — `verify:tarball` and `verify:site` were both added this week
+  and would have been found only by reading `package.json`.
+- The three `verify:*` get their own block with the reason they are not in `npm run check`: each
+  needs the network or an artifact `check` does not build, and `check` staying offline is a
+  property `tests/README.md` opens with.
+
+## 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

package/package.json

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