edfcore 0.6.312 → 0.6.313

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.312";
112
+ export declare const VERSION = "0.6.313";
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.312';
82
+ export const VERSION = '0.6.313';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,21 @@ 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.313
10
+
11
+ - **Security.** `vitest` 4.1.11 to 4.1.12, and `npm audit` is back to zero.
12
+ - This is not a regression in 0.6.305. That release closed GHSA-82fw-gwwq-j7x9 — path traversal and
13
+ arbitrary file read via `@vitest/mocker`'s redirect mock — by taking the fix the advisory named at
14
+ the time, 4.1.11, against a stated range of `2.1.0 - 4.1.10`. **The advisory has since been
15
+ widened** to `<= 4.1.11`, with the fix moved to 4.1.12, so the version that was the remedy became
16
+ one of the affected ones.
17
+ - Worth noting for anyone reading the audit on this repository: `npm audit fix` cannot apply either
18
+ of these on its own, because every dev dependency except `@types/node` is pinned exactly. A
19
+ same-minor security fix still needs a manifest edit here, so a clean `npm audit` is a thing to
20
+ check rather than a thing to assume.
21
+ - Nothing published is affected — `npm audit --omit=dev` was zero throughout, since the package has
22
+ no runtime dependencies. The whole suite ran on the new runner first: 9,199 tests across 630 files.
23
+
9
24
  ## 0.6.312
10
25
 
11
26
  - TypeScript 5.9.3 to **6.0.3**, which Microsoft's own 6.0 announcement calls "the bridge between
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.6.312",
3
+ "version": "0.6.313",
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",
@@ -59,7 +59,7 @@
59
59
  "@types/node": "^26.6.5",
60
60
  "fast-check": "4.10.2",
61
61
  "typescript": "6.0.3",
62
- "vitest": "4.1.11"
62
+ "vitest": "4.1.12"
63
63
  },
64
64
  "scripts": {
65
65
  "build": "tsc -p config/tsconfig.build.json",
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.312';
96
+ export const VERSION = '0.6.313';