edfcore 0.4.26 → 0.4.27
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.27";
|
|
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.27
|
|
10
|
+
|
|
11
|
+
- **Fixed** `AGENTS.md` stating "there are no binary files in git". Six EDF/BDF files have been
|
|
12
|
+
committed under `tests/corpus/golden/` since 0.2.34, and `tests/README.md` explains why they
|
|
13
|
+
must be: regenerating them with `support/writer.ts` would make the pyEDFlib comparison circular.
|
|
14
|
+
An agent trusting that sentence would treat them as strays.
|
|
15
|
+
|
|
9
16
|
## 0.4.26
|
|
10
17
|
|
|
11
18
|
- **Fixed** the documentation site footer reading "MIT licensed. Version 0.1.0." on every page. It
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED