edfcore 0.4.194 → 0.4.195

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.194";
112
+ export declare const VERSION = "0.4.195";
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.194';
82
+ export const VERSION = '0.4.195';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,14 @@ 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.195
10
+
11
+ - **Recorded** why `v0.1.1` has no tag, the last unexplained hole in the version history. It is not
12
+ a consumed number like 0.2.29: it shipped to npm and is installable. It predates
13
+ `scripts/release.mjs` by hours — the bump rode inside an ordinary commit, the publish was done by
14
+ hand, and 0.1.2 fifty minutes later was the first release the script cut. Every other version in
15
+ this file is either tagged or says it was never released.
16
+
9
17
  ## 0.4.194
10
18
 
11
19
  - **Added** the missing `0.2.29` entry. Four numbers have been consumed by a release that failed
@@ -4590,6 +4598,11 @@ feature is a minor under semver, and nineteen patch bumps read as nineteen bug f
4590
4598
  `toPhysical` call. The type stops you reading the gain; it does not gate the call.
4591
4599
  - **Fixed** three README links that 404ed on npmjs.com.
4592
4600
 
4601
+ Published by hand and never tagged, which is why `v0.1.1` is absent while every version around it
4602
+ has a tag. The bump rode inside a34ffd0 rather than a `Release v0.1.1` commit, and the package went
4603
+ to npm at 03:55 on 2026-08-03. `scripts/release.mjs` was added the same day, and 0.1.2 went out
4604
+ fifty minutes later as the first release it cut. This is the last version published without it.
4605
+
4593
4606
  ## 0.1.0
4594
4607
 
4595
4608
  First release. Reads EDF, EDF+, BDF and BDF+ with real random access.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.194",
3
+ "version": "0.4.195",
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.194';
96
+ export const VERSION = '0.4.195';