edfcore 0.4.365 → 0.4.366

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.365";
112
+ export declare const VERSION = "0.4.366";
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.365';
82
+ export const VERSION = '0.4.366';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,21 @@ 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.366
10
+
11
+ - **Added** a check that every version number this repository cites is one it released. The
12
+ codebase explains itself in release numbers — docblocks say "fixed in 0.3.56", the documentation
13
+ pages date every behaviour they describe, the changelog cross-references itself — and there are
14
+ several hundred such citations across 248 files, none of which had ever been checked.
15
+ - They rot silently in two directions: a transposed digit points a reader at nothing, and a
16
+ citation written while a version is still being cut names a number that never shipped, which is
17
+ the same failure the fourteen changelog holes were. A wrong version number looks exactly like a
18
+ right one to a compiler, a linter and a human skimming a diff.
19
+ - The hard part is telling a version from everything else shaped like one, since this tree is full
20
+ of EDF startdates and starttimes, spec clauses like `2.1.1` and runtime floors like `22.12.0`. A
21
+ loose scan reports forty-five of those and no real defects; `0.` with no leading zero separates
22
+ them exactly, and that narrowing is asserted against the lookalikes rather than left to luck.
23
+
9
24
  ## 0.4.365
10
25
 
11
26
  - **Added** a check that the layer table in `AGENTS.md` names the modules that are actually at each
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.365",
3
+ "version": "0.4.366",
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.365';
96
+ export const VERSION = '0.4.366';