edfcore 0.4.302 → 0.4.303

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.302";
112
+ export declare const VERSION = "0.4.303";
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.302';
82
+ export const VERSION = '0.4.303';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,18 @@ 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.303
10
+
11
+ - **Executed** the request budget on `api-sources.md`: one `HEAD` for the length, `bytes=0-255`,
12
+ one more range for the rest of the header, and one whole record at each end for the timekeeping
13
+ probes — five in total, with the caller's headers on all five. That is the paragraph a reader
14
+ consults before pointing this at S3, and every clause is a cost they are budgeting.
15
+ - The count was pinned elsewhere against a literal; the composition was prose, and so was the
16
+ promise about headers — the clause with a security shape, since one request quietly going out
17
+ without the configured `Authorization` 403s in production and nowhere else. All of it is now
18
+ driven through an injected `fetch`, which the suite requires of anything touching the network
19
+ and which is also how the page tells a reader to test their own adapter.
20
+
9
21
  ## 0.4.302
10
22
 
11
23
  - **Made** `api-reading.md`'s read counts the expectation rather than a second statement of it.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.302",
3
+ "version": "0.4.303",
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.302';
96
+ export const VERSION = '0.4.303';