edfcore 0.4.207 → 0.4.208
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 +9 -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.208";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,15 @@ 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.208
|
|
10
|
+
|
|
11
|
+
- **Fixed** the one lint warning the repository has been carrying: a non-null assertion on
|
|
12
|
+
`recordOnsetTicks[0]` in `annotation-timebase.test.ts`. `noUncheckedIndexedAccess` is on, so the
|
|
13
|
+
index really can be `undefined`, and `!` turned an empty result into arithmetic on `undefined`
|
|
14
|
+
rather than a failure naming itself. It now narrows and throws. `biome check` reports warnings
|
|
15
|
+
without failing, so this sat in every run — and a run that always prints a warning is a run where
|
|
16
|
+
the next one goes unread.
|
|
17
|
+
|
|
9
18
|
## 0.4.207
|
|
10
19
|
|
|
11
20
|
- **Changed** the `--patient` scope guard to derive the commands it probes. Its note says the scope
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED