edfcore 0.4.427 → 0.4.429

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

package/docs/CHANGELOG.md

@@ -6,6 +6,44 @@ 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.429
+
+- **Added** tests for `edfcore validate` exiting 1 because validation failed. The exit-code table on
+  `cli.md` gives `1` two meanings in one row — "the file could not be read, or validation failed" —
+  and only the first was exercised. `runCli` returns `report.ok ? 0 : 1`, and nothing had ever
+  driven it down the `false` side, which is the entire reason the command exists.
+- A CI job gating on conformance branches on that number without reading a word of the output, and
+  it can fail in two opposite ways. A gate that never fires passes every recording, including the
+  ones the library refused to scale, and nobody investigates a green tick. A gate that always fires
+  gets switched off, and the conformance checking goes with it.
+- The second is likelier, and it turns on a boundary now stated as a subject: a warning is not a
+  failure. `LABEL_CONVENTION_NONCONFORMANT` is on almost every real recording, CHB-MIT ships a
+  duplicated channel label, a file marked EDF+C whose onsets drift is a warning because real
+  writers do that, and a zero record duration is legal EDF. A gate rejecting any of those would
+  reject the corpus this library was built to read.
+- `header` on the same refused file exits 0, and that contrast is checked. It reports what the
+  header says and adjudicates nothing, which is what makes asking for a verdict worth doing.
+
+## 0.4.428
+
+- **Added** a check that a version number which never reached npm says so at the heading and says
+  where its work went. Nineteen of the six hundred-odd headings in this file name a version nobody
+  can install; they exist because a reader comparing `npm view edfcore versions` against the file
+  would otherwise find a hole and be unable to tell a lost number from a missing note.
+- `changelog-continuity.test.ts` checks the sequence. What it cannot see is whether a heading tells
+  the truth about itself, which is the half 0.4.307 was about: fourteen entries had been written
+  before their release failed, so each read exactly like one that shipped, with the correction in a
+  different entry further up that a reader landing on `## 0.4.288` never sees.
+- So the marker has to be first — a note further down is a note nobody scrolling to a version
+  reads — and it has to point forward, because "Never released" alone strands the reader with work
+  that exists under a number they now have to search for. The pointer is bounded at twenty patches
+  and every real one is within six, so an incidental mention of some later release cannot stand in
+  for it: the 0.2.29 entry names 0.4.194 as the release that wrote it down, and that is not where
+  its work went.
+- The two forms are kept apart on purpose. A number consumed before a tag was cut never became
+  public at all; a version that was tagged and whose publish then failed is public on GitHub and
+  absent from npm, which is a different thing to be told.
+
 ## 0.4.427
 
 - **Added** a property test for `trimToWindow` against the rule it states rather than the examples

package/package.json

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