edfcore 0.4.381 → 0.4.382

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.381";
112
+ export declare const VERSION = "0.4.382";
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.381';
82
+ export const VERSION = '0.4.382';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,21 @@ 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.382
10
+
11
+ - **Fixed** the docblock at the top of `scripts/release.mjs`, which described the scheme that was
12
+ replaced in 0.4.326: "this script only moves the version forward and creates the GitHub Release;
13
+ `publish.yml` sees that release and publishes to npm". It has created no release and watched no
14
+ release since — the tag it pushes is what publishes — and that paragraph is the first thing
15
+ anyone reads before running the script.
16
+ - `release-model.test.ts` has asserted the trigger, the ordering and the absence of `gh release
17
+ create` since 0.4.327, and every one of those checks passed the whole time. They read what the
18
+ script calls, and a comment calls nothing.
19
+ - So the docblock is checked too, by the affirmative rather than the negative: it has to name the
20
+ pushed tag as what publishes, say outright that the script creates no release, and point at
21
+ `npm run announce`. A docblock rewritten back to the old scheme has to delete those sentences to
22
+ read coherently, and deleting them fails.
23
+
9
24
  ## 0.4.381
10
25
 
11
26
  - **Added** the closure this batch earned: every documentation page has to be named by a test that
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.381",
3
+ "version": "0.4.382",
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.381';
96
+ export const VERSION = '0.4.382';