edfcore 0.4.327 → 0.4.328

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.327";
112
+ export declare const VERSION = "0.4.328";
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.327';
82
+ export const VERSION = '0.4.328';
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.328
10
+
11
+ - **Added** a guard for the release model 0.4.327 introduced. Three files describe it and none of
12
+ them enforced it, and the dangerous edit is small and looks like a revert: putting `release:
13
+ types: [published]` back on `publish.yml` leaves every test green, every workflow valid, and
14
+ `scripts/release.mjs` pushing tags that trigger nothing.
15
+ - That is not hypothetical. It is exactly how 0.4.287 through 0.4.292 were lost — six versions
16
+ tagged, six green CI runs, nothing on npm, found only by looking at the registry. So the trigger
17
+ is asserted from the outside, along with the two orderings the gate depends on: that `ci.yml`
18
+ still runs on a push to main, since the release polls for check runs that would otherwise never
19
+ register, and that `release.mjs` pushes main before it tags rather than after.
20
+
9
21
  ## 0.4.327
10
22
 
11
23
  - **Changed** how publishing is triggered: `publish.yml` now runs on a pushed **tag** rather than
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.327",
3
+ "version": "0.4.328",
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.327';
96
+ export const VERSION = '0.4.328';