edfcore 0.6.146 → 0.6.148

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

package/docs/CHANGELOG.md

@@ -6,6 +6,24 @@ 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.6.148
+
+- **Documented** the rule 0.6.130 and 0.6.140 introduced: the options argument itself has to be an
+  object, in the three formatters and in `cachedSource`.
+- Both pages described the FIELDS and neither described the argument, which is the whole of the
+  defect — `formatAnnotations(annotations, 20)` had no `maxItems` on it, so the limit read as
+  absent and every annotation printed with nothing saying so.
+- `undefined` and `null` still mean "no options", and the tables say so.
+
+## 0.6.147
+
+- **Documented** the `out` rules 0.6.134 and 0.6.145 introduced, on the page that describes `out`.
+- `api-primitives.md` said `out` was checked for LENGTH and stopped there, which was the whole
+  defect: an `Int32Array` handed to `toPhysical` truncated every physical value, and for a bit
+  value below 1 the call returned a buffer of zeros as if it were the signal.
+- The `digital` argument's rule is stated too — it needs a length, and the first of its elements
+  must be a number — because a string has a length and its characters are not numbers.
+
 ## 0.6.146
 
 - **Documented** what `httpSource` does with a failure from the client itself: the HEAD probe's

package/package.json

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