edfcore 0.4.483 → 0.4.485

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

package/docs/CHANGELOG.md

@@ -6,6 +6,36 @@ 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.485
+
+- **Added** the edge cases for the sub-second start offset, which is documented as `[0, 1)` and
+  was enforced by two comparisons that could both be relaxed with the suite green. The fixtures
+  that reach them use 1.5 s and 3 s — outside by a margin — so nothing had ever sat on the edge.
+- An offset of exactly 1.0 s is not an exotic value. It is what a writer produces the first time
+  it puts the same second in both fields, and it means every time edfcore publishes for that file
+  is a second out. `START_OFFSET_OUT_OF_RANGE` exists to say so, and quotes the interval it is
+  applying.
+- Both ends, in both paths: record 0's own onset and the value derived for a chunk that starts
+  later. Zero is checked as well, because it is the CLOSED end and the overwhelmingly common case
+  — a check that refused the boundary there would report every conforming file there is. One tick
+  below a second is the largest value the interval admits, and is accepted.
+- The EDF+D case goes with it: the same derived value carries no implication on a file whose
+  marker is for gaps, so the refusal is about the interval on a file claiming continuity rather
+  than about the arithmetic.
+
+## 0.4.484
+
+- **Moved** the 31 MB fixture builds in `read-pattern.test.ts` into a `beforeAll` with a budget of
+  its own. All three builders already memoised, so only the first caller paid — but "the first
+  caller" is a test body with vitest's five-second default, and building 31 MB of records inside
+  it is most of that on an idle machine and more than it on a loaded one.
+- The two tests that happen to ask first, one per fixture, then fail on a timeout that has nothing
+  to do with what they assert. Both were seen failing under coverage instrumentation while the
+  same run passed without it, which is the shape of failure that gets rerun rather than read.
+- This is what 0.4.417 and 0.4.418 did for `spec-references.test.ts`, in that order and for the
+  same reason: memoising alone moves the cost onto whichever test runs first, and a `beforeAll` is
+  where a cost belonging to the file rather than to one case is supposed to sit.
+
 ## 0.4.483
 
 - **Added** the whitespace-at-the-ends cases for the prefiltering conformance check, and a comment

package/package.json

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