edfcore 0.4.213 → 0.4.215

package/dist/constants.d.ts

@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
     readonly reserved: 224;
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export declare const VERSION = "0.4.213";
+export declare const VERSION = "0.4.215";
 //# sourceMappingURL=constants.d.ts.map

package/dist/constants.js

@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
     reserved: 224,
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.4.213';
+export const VERSION = '0.4.215';
 //# sourceMappingURL=constants.js.map

package/docs/CHANGELOG.md

@@ -6,6 +6,25 @@ alone does not tell you whether you were affected.
 edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
 defect; those are called out below.
 
+## 0.4.215
+
+- **Changed** the two severity patterns in `diagnostic-docs.test.ts` to come from the `EdfSeverity`
+  union rather than spelling out `error|warning|info`. They select the sample `formatDiagnostics`
+  lines in the pages that get checked against the code, so a fourth severity would have meant every
+  example using it was simply not looked at. Preventive rather than a fix: unlike the disposition
+  list in 0.4.214 there is no second inventory for severity to fall out of step with, so nothing is
+  wrong today and no canary demonstrates otherwise.
+
+## 0.4.214
+
+- **Fixed** two hand-written copies of the disposition list in `diagnostic-docs.test.ts`. One was
+  the regex that decides which rows of `DISPOSITIONS` the file can see at all, so a fifth
+  disposition would have matched nothing, its codes would never have entered the map, and "every
+  code is documented" would have passed without having heard of them — invisible to the guard
+  rather than merely undocumented. The other was `SECTIONS`, which drives the per-disposition
+  checks. Both now come from the `EdfDiagnosticDisposition` union, and a new disposition without a
+  documented section is now a failure that names it.
+
 ## 0.4.213
 
 - **Fixed** the guard added in 0.4.205, which was the shape of the defect it catches. It compared

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.4.213",
+  "version": "0.4.215",
   "description": "Modern, typed, zero-dependency reader for EDF, EDF+, BDF and BDF+ biosignal files. Works in browsers and Node with true random access.",
   "keywords": [
     "edf",

package/src/constants.ts

@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
 } as const;
 
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.4.213';
+export const VERSION = '0.4.215';