edfcore 0.4.158 → 0.4.160

package/README.md

@@ -428,8 +428,8 @@ like bugs and are not (the pinned scaling expression, `readWindow` always return
 *Background → Design decisions*.
 
 - [`tests/README.md`](https://github.com/tayal-sarthak/edfcore/blob/main/tests/README.md) covers
-  how the suite builds every fixture in memory,
-  and why no binaries are committed.
+  how the suite builds almost every fixture in memory, and why the six small EDF/BDF files under
+  `tests/corpus/golden/` are the deliberate exception.
 
 ## License
 

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

package/docs/CHANGELOG.md

@@ -6,6 +6,22 @@ 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.160
+
+- **Fixed** the README saying `tests/README.md` covers "why no binaries are committed". Six small
+  EDF/BDF files under `tests/corpus/golden/` are committed on purpose, and that page says so in its
+  third sentence, so the pointer contradicted the page it points at.
+
+## 0.4.159
+
+- **Widened** the strict-mode guard to sweep the test suite, and corrected the third copy it found
+  (`tests/unit/header/dates.test.ts`). 0.3.108 swept the doc pages and `src/`, which is how two
+  copies survived in test comments until 0.4.157-0.4.158 — a comment in a test is read by whoever
+  edits that behaviour next, so it is where a retired claim does the most damage.
+- The TypeScript globs are matched on their COMMENTS rather than whole files. Running a prose
+  matcher over code found a test name and the comment beneath it as one phrase; identifiers are not
+  claims about behaviour.
+
 ## 0.4.158
 
 - **Corrected** the second surviving copy of the same claim, in `tests/unit/tal/annotations.test.ts`.

package/package.json

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