edfcore 0.4.293 → 0.4.294

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.293";
112
+ export declare const VERSION = "0.4.294";
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.293';
82
+ export const VERSION = '0.4.294';
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.294
10
+
11
+ - **Added** the last wait the release was missing: whether the version actually reached npm. The
12
+ CI wait from 0.4.244 asks about the commit; `publish.yml` is a different workflow, triggered by
13
+ the release that was just created, and it runs its own `npm run check` afterwards — so it can
14
+ fail on something the commit's checks passed, and the script had always exited 0 before it
15
+ started. That gap cost 0.4.287 through 0.4.292: six versions tagged, six green CI runs, six
16
+ GitHub releases, and nothing on npm, found only by looking.
17
+ - npm is polled rather than the workflow's status, because the question is whether the version is
18
+ installable. On timeout it says the tag, release and commit are all correct and the publish is
19
+ what did not happen, gives the two commands to see why, and warns that re-running the script
20
+ would cut the next version and leave this one a hole — which is exactly how the six were lost.
21
+
9
22
  ## 0.4.293
10
23
 
11
24
  - **Moved** the tarball check out of the test suite, which is the only place it could not live.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.293",
3
+ "version": "0.4.294",
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.293';
96
+ export const VERSION = '0.4.294';