edfcore 0.4.279 → 0.4.280

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.279";
112
+ export declare const VERSION = "0.4.280";
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.279';
82
+ export const VERSION = '0.4.280';
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.280
10
+
11
+ - **Added** a check that the exit-code table on the CLI page is the code the CLI returns.
12
+ `edfcore validate` exiting non-zero is the documented way to gate a CI job on file conformance,
13
+ so those three numbers are an interface a script branches on without parsing a word of output.
14
+ The page stated them and `cli.test.ts` asserted them against literals it holds itself — two
15
+ statements of one contract, kept in step by hand, which is the shape 0.4.267 found in the
16
+ `signals` column table.
17
+ - Each code is produced through both halves of the CLI, because `runCli` returns 0 and 2 and never
18
+ 1: an unreadable file throws, and `src/cli.ts` is what turns that into `error instanceof
19
+ CliUsageError ? 2 : 1`. A check that drove only `runCli` would have quietly never exercised the
20
+ row a CI gate depends on most. The row for 2 is also read for the four cases it lists — unknown
21
+ command, missing file, extra files, bad flag value — and all four are produced.
22
+
9
23
  ## 0.4.279
10
24
 
11
25
  - **Added** a check on which Node built-ins the package imports, read from the README's own
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.279",
3
+ "version": "0.4.280",
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.279';
96
+ export const VERSION = '0.4.280';