edfcore 0.4.380 → 0.4.382

package/dist/constants.d.ts

@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
     readonly reserved: 224;
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export declare const VERSION = "0.4.380";
+export declare const VERSION = "0.4.382";
 //# sourceMappingURL=constants.d.ts.map

package/dist/constants.js

@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
     reserved: 224,
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.4.380';
+export const VERSION = '0.4.382';
 //# sourceMappingURL=constants.js.map

package/docs/CHANGELOG.md

@@ -6,6 +6,37 @@ alone does not tell you whether you were affected.
 edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
 defect; those are called out below.
 
+## 0.4.382
+
+- **Fixed** the docblock at the top of `scripts/release.mjs`, which described the scheme that was
+  replaced in 0.4.326: "this script only moves the version forward and creates the GitHub Release;
+  `publish.yml` sees that release and publishes to npm". It has created no release and watched no
+  release since — the tag it pushes is what publishes — and that paragraph is the first thing
+  anyone reads before running the script.
+- `release-model.test.ts` has asserted the trigger, the ordering and the absence of `gh release
+  create` since 0.4.327, and every one of those checks passed the whole time. They read what the
+  script calls, and a comment calls nothing.
+- So the docblock is checked too, by the affirmative rather than the negative: it has to name the
+  pushed tag as what publishes, say outright that the script creates no release, and point at
+  `npm run announce`. A docblock rewritten back to the old scheme has to delete those sentences to
+  read coherently, and deleting them fails.
+
+## 0.4.381
+
+- **Added** the closure this batch earned: every documentation page has to be named by a test that
+  is about that page. `docs-coverage.test.ts` sweeps all of them for exported names and
+  `doc-snippets-compile.test.ts` compiles every fence, but a generic sweep says nothing about
+  whether a page's own tables, worked numbers and refusals have ever been executed.
+- Several pages had none until recently. `edf-format.md` and `physical-values.md` were the first
+  two found that way, `migrating-to-0-3.md`, `api-validate.md` and `quick-start.md` the next three,
+  and each turned out to be carrying claims worth checking — one of them a wrong one. All
+  twenty-three are named now, and a page added tomorrow either gets a test or fails this and says
+  which page it is.
+- The sweeps are excluded from counting rather than forbidden from naming a page. The first version
+  forbade it and was wrong to: `docs-coverage.test.ts` anchors its own non-vacuity with
+  `DOCS.has('api-helpers.md')`, which is reasonable and is not a check about that page. What
+  matters is that no page is covered only by a sweep.
+
 ## 0.4.380
 
 - **Added** enforcement for the fixture policy in `tests/README.md`: "No file from teuniz.net,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.4.380",
+  "version": "0.4.382",
   "description": "Modern, typed, zero-dependency reader for EDF, EDF+, BDF and BDF+ biosignal files. Works in browsers and Node with true random access.",
   "keywords": [
     "edf",

package/src/constants.ts

@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
 } as const;
 
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.4.380';
+export const VERSION = '0.4.382';