edfcore 0.4.198 → 0.4.200

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.198";
112
+ export declare const VERSION = "0.4.200";
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.198';
82
+ export const VERSION = '0.4.200';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,22 @@ 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.200
10
+
11
+ - **Fixed** `scripts/release.mjs` consuming a version number when its own checks fail. The bump is
12
+ written before lint, typecheck, tests and build run, so a run that stopped there left the higher
13
+ version on disk and the next run produced the one after it. Four numbers have been lost that way
14
+ — 0.2.29, 0.2.36, 0.2.59 and 0.4.176 — and each cost an entry in this file explaining a hole
15
+ instead of a release. The checks now run inside a `try`, and a failure puts the three version
16
+ files back before exiting, so the number stays free for the run that fixes the problem.
17
+
18
+ ## 0.4.199
19
+
20
+ - **Corrected** the title of `documented-examples.test-d.ts`, which read "The documented examples
21
+ in the docs compile". Three do. The three pages it covers carry 55 `ts` fences, and each covered
22
+ example needs a compiled twin written by hand, so the set is small on purpose — but a maintainer
23
+ reading the title would think a new snippet was already checked.
24
+
9
25
  ## 0.4.198
10
26
 
11
27
  - **Corrected** the list of budget readers in `src/options.ts`. It named six modules; eight read
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.198",
3
+ "version": "0.4.200",
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.198';
96
+ export const VERSION = '0.4.200';