edfcore 0.6.305 → 0.6.306

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
109
109
  readonly reserved: 224;
110
110
  };
111
111
  /** Published package version. Kept in sync with package.json by a test. */
112
- export declare const VERSION = "0.6.305";
112
+ export declare const VERSION = "0.6.306";
113
113
  //# sourceMappingURL=constants.d.ts.map
package/dist/constants.js CHANGED
@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
79
79
  reserved: 224,
80
80
  };
81
81
  /** Published package version. Kept in sync with package.json by a test. */
82
- export const VERSION = '0.6.305';
82
+ export const VERSION = '0.6.306';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,19 @@ alone does not tell you whether you were affected.
6
6
  edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
7
7
  defect; those are called out below.
8
8
 
9
+ ## 0.6.306
10
+
11
+ - **Fixed** CI typechecking against older Node types than a contributor's machine resolves. The
12
+ lockfile pinned `@types/node` at 26.1.2 while the manifest range was `^26.1.2` and 26.6.5 was
13
+ current — and every workflow installs with `npm ci`, which honours the lockfile, whereas a fresh
14
+ clone running `npm install` takes the newest match in the range.
15
+ - So the two disagreed by five minor versions of the type definitions for the runtime this package
16
+ targets, in a repository whose `typecheck` script runs **two** configs specifically to control what
17
+ can see Node and DOM globals. A type error introduced against one would pass on the other, in
18
+ whichever direction the author happened not to be.
19
+ - Lockfile and range both now name 26.6.5. Nothing in `src/` changed: both typecheck configs are
20
+ clean against the newer definitions, and the suite is unchanged at 9,191 tests across 628 files.
21
+
9
22
  ## 0.6.305
10
23
 
11
24
  - **Security.** Four advisories in the dev toolchain, all now closed — `npm audit` reports zero.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.6.305",
3
+ "version": "0.6.306",
4
4
  "description": "Modern, typed, zero-dependency reader for EDF, EDF+, BDF and BDF+ biosignal files. Works in browsers and Node with true random access.",
5
5
  "keywords": [
6
6
  "edf",
@@ -56,7 +56,7 @@
56
56
  },
57
57
  "devDependencies": {
58
58
  "@biomejs/biome": "2.5.6",
59
- "@types/node": "^26.1.2",
59
+ "@types/node": "^26.6.5",
60
60
  "fast-check": "4.9.0",
61
61
  "typescript": "5.9.3",
62
62
  "vitest": "4.1.11"
package/src/constants.ts CHANGED
@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
93
93
  } as const;
94
94
 
95
95
  /** Published package version. Kept in sync with package.json by a test. */
96
- export const VERSION = '0.6.305';
96
+ export const VERSION = '0.6.306';