edfcore 0.3.63 → 0.3.65

package/CHANGELOG.md

@@ -6,6 +6,50 @@ 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.3.65
+
+- **Fixed** `api-errors.md` publishing the wrong signature for `isEdfError` and calling a cast
+  mandatory that the compiler does not require.
+  - The page said `function isEdfError(value: unknown): value is EdfError`. It returns
+    `value is AnyEdfError` — the discriminated union over the seven concrete classes.
+  - Around that it built a **Note** explaining that "the cast in each branch is load-bearing" and
+    that "reaching for `error.budgetBytes` without the cast is a compile error", with three `as`
+    casts in the snippet to match. None of it is true: the snippet compiles without them under
+    edfcore's own `tsconfig.json`. `src/errors.ts` says why in the docblock on `AnyEdfError` — the
+    union exists precisely so that switching on `edfErrorKind` reaches the extra fields "without
+    one". The page documented the problem the union was added to solve as though it were still
+    there.
+- The snippet is now in `tests/types/documented-examples.test-d.ts` alongside the other two, so
+  `npm run typecheck` compiles it: if a cast ever became necessary, the build would say so rather
+  than a paragraph.
+  - Adding it immediately caught a second error in the same snippet. `EdfRangeError.available` is a
+    `RecordRange`, not a count, so the helper the page calls `clampToFile(error.available)` cannot
+    take a `number`.
+- The comparison against the page is now indentation-insensitive, because a page-level fragment sits
+  at column 0 and a compiled copy has to live inside a function. The snippet's `switch` arms were
+  reflowed to the form this project's formatter produces, so the page shows code that would survive
+  `biome check`.
+
+## 0.3.64
+
+- **Fixed** the pre-0.2 status text still on the website, which contradicted the package and, in one
+  case, the page it linked to in the same sentence.
+  - `concepts.md` said the pyEDFlib comparison harness "does not exist yet in 0.1" and linked, in
+    that sentence, to `physical-values.md`, which says it has existed since 0.2.34-0.2.48. So the
+    one claim a reader would check was denied by the page they were sent to check it on.
+  - `installation.md` said "edfcore is at 0.1.0" and that an element-by-element comparison against
+    pyEDFlib is "still missing"; `api-primitives.md` tabled `VERSION` as `'0.1.0'` and repeated it
+    in prose as "at the time of writing".
+  - Three pages scoped a still-true statement to a dead series — "edfcore has no other lifetime
+    mechanism in 0.1". The claim holds (`Symbol.asyncDispose` is not Baseline); the version scope
+    did not.
+- The `VERSION` row no longer spells a number at all. A version written into a table is stale the
+  next release, which is how this started.
+- `tests/integration/readme-status.test.ts` now sweeps every docs page for two present-tense shapes:
+  "edfcore is at X.Y.Z" that is not the published version, and "in X.Y" scoping a claim to a series
+  that is no longer this one. Past-tense history — "renamed in 0.3.0", "fixed in 0.2.63", "since
+  0.2.34-0.2.48" — is correct forever and is deliberately not matched.
+
 ## 0.3.63
 
 - **Fixed** `diagnostics.md`'s always-fatal table, which said "Nine codes are always fatal", listed

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

package/package.json

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