edfcore 0.4.224 → 0.4.226

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.224";
+export declare const VERSION = "0.4.226";
 //# 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.224';
+export const VERSION = '0.4.226';
 //# 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.226
+
+- **Added** a recovery message for the one release step the 0.4.200 revert cannot reach. By the
+  time `gh release create` runs, the bump is committed and the tag is pushed, so there is nothing
+  local to undo — and `publish.yml` triggers on a PUBLISHED release rather than on a tag, so a
+  failure there leaves a version that exists in git and never reaches npm. Nothing in the
+  repository would notice: `changelog-continuity.test.ts` checks this file against itself, and the
+  entry would be present and correct. The script now says how to finish the release, and warns that
+  re-running it would cut the next version and leave this one a hole.
+
+## 0.4.225
+
+- **Fixed** `npm run format` being unable to produce a tree `npm run lint` accepts. `format` was
+  `biome format --write`, which reformats but does not run Biome's assists; `lint` is `biome check`,
+  which reports `organizeImports` as an error. So an unsorted import block was a failure that the
+  repository's own formatter reported nothing about and could not repair — running format, seeing
+  "no fixes applied", and then failing lint on the same file. It now runs the assists too, with the
+  linter disabled so that formatting stays formatting and lint findings are still fixed on purpose
+  rather than by a command named `format`.
+
 ## 0.4.224
 
 - **Changed** the barrel type parser to live once, in `tests/support/barrel-types.ts`, instead of

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.4.224",
+  "version": "0.4.226",
   "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",
@@ -68,7 +68,7 @@
     "test:watch": "vitest --config config/vitest.config.ts",
     "test:scratch": "vitest run --config config/vitest.scratch.config.ts",
     "lint": "biome check --error-on-warnings .",
-    "format": "biome format --write .",
+    "format": "biome check --write --linter-enabled=false .",
     "check": "npm run lint && npm run typecheck && npm run build && npm run test",
     "corpus:fetch": "node scripts/fetch-corpus.mjs",
     "release": "node scripts/release.mjs",

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.224';
+export const VERSION = '0.4.226';