edfcore 0.4.218 → 0.4.219
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.
- package/dist/constants.d.ts +1 -1
- package/dist/constants.js +1 -1
- package/docs/CHANGELOG.md +8 -0
- package/package.json +1 -1
- package/src/constants.ts +1 -1
package/dist/constants.d.ts
CHANGED
|
@@ -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.
|
|
112
|
+
export declare const VERSION = "0.4.219";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,14 @@ 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.219
|
|
10
|
+
|
|
11
|
+
- **Added** the same check to `corpus-parity.test.ts`, and deliberately did not gate it on the
|
|
12
|
+
corpus being present. Every other test in that file skips without `npm run corpus:fetch`, and CI
|
|
13
|
+
never fetches, so a gated version would have been the one check there that runs nowhere. The
|
|
14
|
+
goldens are committed, which is all it needs — and on a file whose normal state is "skipped", a
|
|
15
|
+
golden nothing compares against is especially hard to see.
|
|
16
|
+
|
|
9
17
|
## 0.4.218
|
|
10
18
|
|
|
11
19
|
- **Added** the same check to `mne-parity.test.ts`: a case for every committed `.mne.json`. This
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED