edfcore 0.4.219 → 0.4.221

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.219";
+export declare const VERSION = "0.4.221";
 //# 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.219';
+export const VERSION = '0.4.221';
 //# sourceMappingURL=constants.js.map

package/docs/CHANGELOG.md

@@ -6,6 +6,28 @@ 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.221
+
+- **Corrected** the title of `docs-coverage.test.ts` now that 0.4.220 gave it a list of exceptions.
+  "Every exported symbol is documented somewhere" was true of what it checked before and is not
+  true of what it checks now — fourteen types are exempted by name. Leaving it would have been the
+  defect this file exists to catch, one level up: a claim of total coverage standing over a check
+  that does not have it.
+
+## 0.4.220
+
+- **Added** the missing half of `docs-coverage.test.ts`. Its title is "Every exported symbol is
+  documented somewhere", but it enumerates `Object.keys` of the barrels — runtime values only,
+  since a type has nothing to enumerate — and the comment where the other half should have been
+  claimed "types are documented under their own names too". Fourteen are not:
+  `EdfAnnotationWindow`, `EdfCodeCount`, `EdfDiagnosticSummary`, `EdfEnvelopeChunk`,
+  `EdfEnvelopeSignal`, `EdfPhysicalEnvelope`, `EdfStatusWord`, `EdfTriggerEvent`,
+  `EnvelopeSelection`, `FormatAnnotationsOptions`, `FormatHeaderOptions`, `FormatReportOptions`,
+  `StreamSelection` and `TriggerSelection` appear on no page. Type names now come from the
+  `export type { … }` blocks, the fourteen are recorded as named debt so a fifteenth fails, and
+  documenting one fails a second check until it is struck off — so the list shrinks rather than
+  outliving the gap. **Fixing the fourteen is a documentation job, not this release.**
+
 ## 0.4.219
 
 - **Added** the same check to `corpus-parity.test.ts`, and deliberately did not gate it on the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.4.219",
+  "version": "0.4.221",
   "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.219';
+export const VERSION = '0.4.221';