edfcore 0.6.306 → 0.6.308

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

package/docs/CHANGELOG.md

@@ -6,6 +6,24 @@ 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.6.308
+
+- `fast-check` 4.9.0 to 4.10.2, the generator behind 26 property files and 174 properties.
+- Worth running rather than assuming: every property here is pinned to a fixed `seed`, so a change
+  in the generator changes which values that seed produces. A bump is therefore a fresh draw against
+  the same invariants, not a no-op — all 174 hold, and the suite is unchanged at 9,191 tests.
+- The 4.10 fixes themselves are for the `interruptAfterTimeLimit` plugin, which this repository does
+  not use; the bump is hygiene, and the re-draw is the part with value.
+
+## 0.6.307
+
+- `@biomejs/biome` 2.5.6 to 2.5.15, with `biome.json`'s `$schema` migrated to match. The two travel
+  together: a CLI newer than the schema the config names reports a `deserialize` notice on every run,
+  which is noise on the tool that gates `npm run check`.
+- This is the linter and formatter for the whole repository, so it was checked against the tree
+  before shipping rather than after: nine patch versions of new and changed rules found nothing new —
+  the same two known `info`-level findings and no errors.
+
 ## 0.6.306
 
 - **Fixed** CI typechecking against older Node types than a contributor's machine resolves. The

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.6.306",
+  "version": "0.6.308",
   "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",
@@ -55,9 +55,9 @@
     "node": ">=22.12.0"
   },
   "devDependencies": {
-    "@biomejs/biome": "2.5.6",
+    "@biomejs/biome": "2.5.15",
     "@types/node": "^26.6.5",
-    "fast-check": "4.9.0",
+    "fast-check": "4.10.2",
     "typescript": "5.9.3",
     "vitest": "4.1.11"
   },

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