edfcore 0.4.229 → 0.4.230

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
109
109
  readonly reserved: 224;
110
110
  };
111
111
  /** Published package version. Kept in sync with package.json by a test. */
112
- export declare const VERSION = "0.4.229";
112
+ export declare const VERSION = "0.4.230";
113
113
  //# sourceMappingURL=constants.d.ts.map
package/dist/constants.js CHANGED
@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
79
79
  reserved: 224,
80
80
  };
81
81
  /** Published package version. Kept in sync with package.json by a test. */
82
- export const VERSION = '0.4.229';
82
+ export const VERSION = '0.4.230';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,19 @@ alone does not tell you whether you were affected.
6
6
  edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
7
7
  defect; those are called out below.
8
8
 
9
+ ## 0.4.230
10
+
11
+ - **Added** a check on the three packaging promises in the README's compatibility list — zero
12
+ runtime dependencies, three entry points with no environment conditions in the exports map, and
13
+ ESM only. What the package *contains* is well covered: `api-surface.test.ts` counts the exports
14
+ and `public-api.test.ts` walks the module graph. Nothing read the manifest that says how it is
15
+ shipped. Adding a dependency is one `npm install --save` away and the tree stays green — nothing
16
+ imports it, so no test fails, and "zero-dependency" stops being true in the one place a reader
17
+ looks before installing. An environment condition next to `default` is the same shape of edit.
18
+ Every export and `bin` target is also checked to exist in the build; `publint` and
19
+ `@arethetypeswrong/cli` cover a stronger version of that, but they run in `publish.yml` only —
20
+ after the tag is pushed, in the window 0.4.226 is about.
21
+
9
22
  ## 0.4.229
10
23
 
11
24
  - **Added** a check that the Node floor is one number. It is written down eleven times — the
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.229",
3
+ "version": "0.4.230",
4
4
  "description": "Modern, typed, zero-dependency reader for EDF, EDF+, BDF and BDF+ biosignal files. Works in browsers and Node with true random access.",
5
5
  "keywords": [
6
6
  "edf",
package/src/constants.ts CHANGED
@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
93
93
  } as const;
94
94
 
95
95
  /** Published package version. Kept in sync with package.json by a test. */
96
- export const VERSION = '0.4.229';
96
+ export const VERSION = '0.4.230';