edfcore 0.4.203 → 0.4.205

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.203";
112
+ export declare const VERSION = "0.4.205";
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.203';
82
+ export const VERSION = '0.4.205';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,25 @@ 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.205
10
+
11
+ - **Added** a guard that the four copies of the documentation section list agree. The `z.enum` in
12
+ `content.config.ts` is written out again in `DocsNav.astro`, `llms.txt.ts` and `llms-full.txt.ts`,
13
+ and each groups pages by walking its own array — so a name in the enum and not in an array is a
14
+ section whose pages render at their URL and appear in no index, missing from the sidebar and from
15
+ both files agents read. DocsNav's docblock says a fifth section "fails the build rather than going
16
+ missing from the sidebar", which held only while four hand-written lists happened to match, and
17
+ adding to the enum is the very edit that breaks it. `astro check` sees four well-typed arrays.
18
+
19
+ ## 0.4.204
20
+
21
+ - **Corrected** the reason `publish.yml` pins npm. The step said trusted publishing needs
22
+ >= 11.5.1, which was true when f363feb added it on 2026-08-01 — but ed89f67 moved the workflow
23
+ to a granular access token two days later, and the note further down the same file now explains
24
+ that registering trusted publishing returns 400 for this package. One comment justified the step
25
+ by a mechanism another said was unavailable. The pin still earns its place; the reason is now
26
+ the one that applies.
27
+
9
28
  ## 0.4.203
10
29
 
11
30
  - **Corrected** the docblock of `changelog-continuity.test.ts`, which had gone stale twice over. It
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.203",
3
+ "version": "0.4.205",
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.203';
96
+ export const VERSION = '0.4.205';