edfcore 0.4.201 → 0.4.203

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.201";
112
+ export declare const VERSION = "0.4.203";
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.201';
82
+ export const VERSION = '0.4.203';
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.203
10
+
11
+ - **Corrected** the docblock of `changelog-continuity.test.ts`, which had gone stale twice over. It
12
+ described a consumed number in the present tense, which 0.4.200 ended; and it quoted
13
+ `scripts/release.mjs` verbatim — "the way 0.2.29, 0.2.36 and 0.2.59 are" — a sentence 0.4.197
14
+ and 0.4.202 have both since rewritten. A quotation is the one kind of reference that cannot
15
+ survive edits to its source, so it is now a paraphrase that stays true.
16
+
17
+ ## 0.4.202
18
+
19
+ - **Corrected** the two places in `scripts/release.mjs` that still describe a consumed number as
20
+ something that happens. 0.4.200 stopped it, and left its own file saying a failed run "consumes"
21
+ the number in the present tense — once in the note above the heading check and once in the error
22
+ that check prints. The note now says what that check still earns: a heading typed wrong by hand,
23
+ and a run that dies after the commit exists, neither of which the revert reaches.
24
+
9
25
  ## 0.4.201
10
26
 
11
27
  - **Fixed** the half of 0.4.200 it left out. The lockfile sync runs after the bump and before the
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.201",
3
+ "version": "0.4.203",
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.201';
96
+ export const VERSION = '0.4.203';