edfcore 0.4.206 → 0.4.208

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.206";
112
+ export declare const VERSION = "0.4.208";
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.206';
82
+ export const VERSION = '0.4.208';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,23 @@ 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.208
10
+
11
+ - **Fixed** the one lint warning the repository has been carrying: a non-null assertion on
12
+ `recordOnsetTicks[0]` in `annotation-timebase.test.ts`. `noUncheckedIndexedAccess` is on, so the
13
+ index really can be `undefined`, and `!` turned an empty result into arithmetic on `undefined`
14
+ rather than a failure naming itself. It now narrows and throws. `biome check` reports warnings
15
+ without failing, so this sat in every run — and a run that always prints a warning is a run where
16
+ the next one goes unread.
17
+
18
+ ## 0.4.207
19
+
20
+ - **Changed** the `--patient` scope guard to derive the commands it probes. Its note says the scope
21
+ is "DERIVED from behaviour rather than written down twice", and the scope was — but the list of
22
+ commands to try it on was spelled out, and again as a regex alternation on the next line. A
23
+ seventh command would have been probed by neither, so the banner could omit it and the guard
24
+ would still pass. Both now come from the usage banner itself.
25
+
9
26
  ## 0.4.206
10
27
 
11
28
  - **Added** a guard that `--help` offers exactly the commands the CLI will dispatch. `cli-run.ts`
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.206",
3
+ "version": "0.4.208",
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.206';
96
+ export const VERSION = '0.4.208';