edfcore 0.4.243 → 0.4.244

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.243";
112
+ export declare const VERSION = "0.4.244";
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.243';
82
+ export const VERSION = '0.4.244';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,20 @@ 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.244
10
+
11
+ - **Added** a wait for CI before the GitHub release is created, which is what stops a green local
12
+ run from becoming a version that never reaches npm. `npm run check` runs on the machine cutting
13
+ the tag, and that is not the same question as whether it passes: twice this week a check was
14
+ green here and red on every runner — one read a file whose tsconfig lives in
15
+ `website/node_modules`, which CI does not install, and one required the gitignored
16
+ `tests/scratch/` to exist. Between them 0.4.231–0.4.236 and 0.4.241–0.4.242 were tagged and
17
+ never published, eight numbers refused by `publish.yml` long after this script had exited 0.
18
+ The script now polls the check runs for the exact commit it pushed and refuses to open the door
19
+ to npm if any of them fails. That turns a silent hole into a stop with the tag intact and the
20
+ version still recoverable by `gh release create` — the same recovery 0.4.226 wrote the message
21
+ for. It gives up after twenty minutes and says so rather than hanging.
22
+
9
23
  ## 0.4.243
10
24
 
11
25
  - **Fixed** the layout-table check added in 0.4.241, which compared `tests/README.md` against the
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.243",
3
+ "version": "0.4.244",
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.243';
96
+ export const VERSION = '0.4.244';