edfcore 0.4.190 → 0.4.191
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 +7 -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.191";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,13 @@ 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.191
|
|
10
|
+
|
|
11
|
+
- **Corrected** the download size on `npm run corpus:fetch`. `tests/README.md` said ~59 MB, which
|
|
12
|
+
was exact for the five files in the manifest when it was written on 2026-08-01. CHB-MIT arrived
|
|
13
|
+
six days later and nearly doubled it; the manifest now totals 101,665,332 bytes across seven
|
|
14
|
+
files. Someone deciding whether to run the fetch on a metered connection was off by 42 MB.
|
|
15
|
+
|
|
9
16
|
## 0.4.190
|
|
10
17
|
|
|
11
18
|
- **Widened** the docs-coverage guard to derive what `./validate` and `./node` export instead of
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED