edfcore 0.4.210 → 0.4.212

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.210";
112
+ export declare const VERSION = "0.4.212";
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.210';
82
+ export const VERSION = '0.4.212';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,23 @@ 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.212
10
+
11
+ - **Added** the guard for 0.4.211, and the counterpart to 0.4.210 on the other side of the repo:
12
+ `npm --prefix website run check` now passes `--minimumFailingSeverity hint`, so the site's type
13
+ check fails on a hint instead of printing one and exiting 0. That is how the JSON-LD hint rode
14
+ along in CI for as long as it did. Both halves of the repository now fail on the quietest thing
15
+ their checkers can say.
16
+
17
+ ## 0.4.211
18
+
19
+ - **Added** `is:inline` to the JSON-LD block in `Base.astro`, clearing the one hint `astro check`
20
+ has been printing. Without it the tag goes through Astro's script processing, which is for code
21
+ it is asked to bundle rather than for a literal payload that must reach the page exactly as
22
+ written — and this one is hand-escaped, so passing it through anything is the wrong default.
23
+ `astro check` now reports 0 errors, 0 warnings and 0 hints; the built `index.html` carries the
24
+ same graph it did before.
25
+
9
26
  ## 0.4.210
10
27
 
11
28
  - **Added** the guard for 0.4.208 and 0.4.209: `npm run lint` now passes `--error-on-warnings`, so
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.210",
3
+ "version": "0.4.212",
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.210';
96
+ export const VERSION = '0.4.212';