edfcore 0.4.238 → 0.4.239

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.238";
112
+ export declare const VERSION = "0.4.239";
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.238';
82
+ export const VERSION = '0.4.239';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,18 @@ 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.239
10
+
11
+ - **Added** the guard for what 0.4.237 fixed: no test may glob a TypeScript or `.astro` file out
12
+ of `website/`. `?raw` returns bytes, but the path still goes through vite's transform, and the
13
+ transform resolves that file's nearest tsconfig — which for anything under `website/` extends
14
+ `astro/tsconfigs/strict` out of `website/node_modules`, a directory the CI `check` job never
15
+ installs. That is a failure mode with no local symptom at all: the command passes on the machine
16
+ cutting the release and dies on every runner, which is exactly how six versions came to be
17
+ tagged and never published. Markdown stays allowed, because no JavaScript tooling reads a `.md`
18
+ file's tsconfig. The scanner uses `readFileSync` rather than a glob, on the same reasoning one
19
+ level up.
20
+
9
21
  ## 0.4.238
10
22
 
11
23
  - **Fixed** the README undercounting the documentation site. It said "an Astro build with twenty
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.238",
3
+ "version": "0.4.239",
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.238';
96
+ export const VERSION = '0.4.239';