edfcore 0.4.239 → 0.4.240

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.239";
112
+ export declare const VERSION = "0.4.240";
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.239';
82
+ export const VERSION = '0.4.240';
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.240
10
+
11
+ - **Extended** the link check added in 0.4.236 to the links that point back at this project by
12
+ absolute URL — nine of them, seven `github.com/.../blob/main/<path>` or `tree/main/<path>` and
13
+ two into `edfcore.vercel.app`. Those rot the same way a relative link does and are harder to
14
+ notice, because they look external and nobody thinks of them as the project's own. This
15
+ repository has already made the move that breaks them: the changelog was `CHANGELOG.md` until
16
+ v0.4.1 and `docs/CHANGELOG.md` after, which `scripts/release.mjs` still has to explain when it
17
+ tells you which spelling to use for which tag — and the README links to that file twice. A
18
+ `blob/main` path is now checked against the working tree, a `vercel.app` URL resolves as an
19
+ internal link, and the README's own `#roadmap` anchor is checked against its headings.
20
+
9
21
  ## 0.4.239
10
22
 
11
23
  - **Added** the guard for what 0.4.237 fixed: no test may glob a TypeScript or `.astro` file out
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.239",
3
+ "version": "0.4.240",
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.239';
96
+ export const VERSION = '0.4.240';