edfcore 0.4.157 → 0.4.159

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.157";
112
+ export declare const VERSION = "0.4.159";
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.157';
82
+ export const VERSION = '0.4.159';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,22 @@ 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.159
10
+
11
+ - **Widened** the strict-mode guard to sweep the test suite, and corrected the third copy it found
12
+ (`tests/unit/header/dates.test.ts`). 0.3.108 swept the doc pages and `src/`, which is how two
13
+ copies survived in test comments until 0.4.157-0.4.158 — a comment in a test is read by whoever
14
+ edits that behaviour next, so it is where a retired claim does the most damage.
15
+ - The TypeScript globs are matched on their COMMENTS rather than whole files. Running a prose
16
+ matcher over code found a test name and the comment beneath it as one phrase; identifiers are not
17
+ claims about behaviour.
18
+
19
+ ## 0.4.158
20
+
21
+ - **Corrected** the second surviving copy of the same claim, in `tests/unit/tal/annotations.test.ts`.
22
+ The assertion was right and its stated reason was not: the array is empty because that fixture is
23
+ conforming, not because strict empties it.
24
+
9
25
  ## 0.4.157
10
26
 
11
27
  - **Corrected** the retired strict-mode claim where it had survived: a doc comment in
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.157",
3
+ "version": "0.4.159",
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.157';
96
+ export const VERSION = '0.4.159';