edfcore 0.4.228 → 0.4.229

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.4.228";
112
+ export declare const VERSION = "0.4.229";
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.4.228';
82
+ export const VERSION = '0.4.229';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,20 @@ 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.4.229
10
+
11
+ - **Added** a check that the Node floor is one number. It is written down eleven times — the
12
+ README's compatibility line, four statements on `installation.md`, two on
13
+ `design-decisions.md`, the `llms.txt` summary handed to agents, and the docblocks in
14
+ `src/index.ts` and `src/cli.ts`, which `removeComments: false` ships verbatim into `dist/*.d.ts`
15
+ as an editor's hover text — and one of the eleven is not prose. The CI matrix's lowest entry is
16
+ the version the suite is actually proven against, while `engines.node` is the version consumers
17
+ are told to have; raising one without the other gives either a package that installs where it
18
+ was never run, or a matrix job on a version nobody may use, and nothing said which. All of them
19
+ are now read against `engines.node`. The scan recognises a requirement and deliberately not
20
+ `Node v24.4.0`, which is the shape `src/bytes/latin1.ts` uses for "the runtime this was verified
21
+ on" — the `v` is what separates a version someone ran from one someone requires.
22
+
9
23
  ## 0.4.228
10
24
 
11
25
  - **Added** a test that actually runs `require()` of the built package from CommonJS. That it
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.228",
3
+ "version": "0.4.229",
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",
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.4.228';
96
+ export const VERSION = '0.4.229';