edfcore 0.4.200 → 0.4.202

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

package/docs/CHANGELOG.md

@@ -6,6 +6,21 @@ 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.202
+
+- **Corrected** the two places in `scripts/release.mjs` that still describe a consumed number as
+  something that happens. 0.4.200 stopped it, and left its own file saying a failed run "consumes"
+  the number in the present tense — once in the note above the heading check and once in the error
+  that check prints. The note now says what that check still earns: a heading typed wrong by hand,
+  and a run that dies after the commit exists, neither of which the revert reaches.
+
+## 0.4.201
+
+- **Fixed** the half of 0.4.200 it left out. The lockfile sync runs after the bump and before the
+  checks, so it sat outside the `try` that puts the version back — and it is the step most likely
+  to fail for a reason unrelated to the code, since it reaches the registry. A failed `npm install
+  --package-lock-only` would still have consumed the number.
+
 ## 0.4.200
 
 - **Fixed** `scripts/release.mjs` consuming a version number when its own checks fail. The bump is

package/package.json

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