edfcore 0.4.319 → 0.4.320

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.319";
112
+ export declare const VERSION = "0.4.320";
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.319';
82
+ export const VERSION = '0.4.320';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,17 @@ 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.320
10
+
11
+ - **Extended** 0.4.319 to the second copy of the harness table. `scripts/golden/README.md` carries
12
+ the complete one — four rows rather than the documentation page's three, because it includes
13
+ `corpus-parity.test.ts`, the only harness whose inputs nobody here chose — and `tests/README.md`
14
+ sends the reader to it for "what each harness claims and how strong that claim is".
15
+ - That copy names each harness by file, which is the stronger form, so a row cannot outlive the
16
+ test it describes. Every named file has to exist, every bit-for-bit row has to belong to a
17
+ harness that compares with `Object.is` and no tolerance, and the MNE bound has to match both the
18
+ constant in the harness and the figure the other table publishes.
19
+
9
20
  ## 0.4.319
10
21
 
11
22
  - **Added** a check that the three cross-implementation harnesses claim on the page exactly what
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.319",
3
+ "version": "0.4.320",
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.319';
96
+ export const VERSION = '0.4.320';