edfcore 0.4.306 → 0.4.308

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.306";
+export declare const VERSION = "0.4.308";
 //# 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.306';
+export const VERSION = '0.4.308';
 //# sourceMappingURL=constants.js.map

package/docs/CHANGELOG.md

@@ -6,6 +6,28 @@ 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.308
+
+- **Added** the guard for what 0.4.307 fixed: a version another entry calls a hole has to say so in
+  its own entry. The list is derived rather than kept — an entry saying "0.4.287 through 0.4.292
+  were never released" declares six, and each of those six must carry the note itself.
+- Nothing here knows what npm holds, because the suite is offline. Checking the changelog against
+  itself is the strongest form available, and it is the failure that actually happened: fourteen
+  entries written before their release failed, each reading like one that shipped, with the
+  correction sitting in a different entry the reader never reaches.
+
+## 0.4.307
+
+- **Marked** the fourteen changelog entries for versions that were never released. Each of them —
+  0.4.231 through 0.4.236, 0.4.241, 0.4.242, and 0.4.287 through 0.4.292 — was written before its
+  release failed, so the entry reads exactly like one that shipped. The correction lived in a
+  different entry further up, which a reader at `## 0.4.288` never sees: they get a normal-looking
+  changelog entry for a version `npm install edfcore@0.4.288` cannot fetch.
+- The older holes already did this right. 0.2.29, 0.2.36, 0.2.59 and 0.4.176 each open by saying
+  "Never released" and naming the version that carried the work, which is the convention
+  `scripts/release.mjs` points at when it tells you to record a consumed number. These fourteen
+  now do the same, and say which version carried them.
+
 ## 0.4.306
 
 - **Built** the file `discontinuous.md` draws and read it. The page opens with a diagram — six
@@ -185,6 +207,8 @@ defect; those are called out below.
 
 ## 0.4.292
 
+> **Never released.** This version was tagged and its publish run failed, so it is not on npm. Everything below shipped in `0.4.293`.
+
 - **Fixed** the tarball check added in 0.4.287, which broke the publish it was written to protect.
   It ran `npm pack --dry-run --json` without `--ignore-scripts`, so `npm pack` ran the pack
   lifecycle — and this package's `prepublishOnly` is `npm run check && npm run build`. The pack
@@ -201,6 +225,8 @@ defect; those are called out below.
 
 ## 0.4.291
 
+> **Never released.** This version was tagged and its publish run failed, so it is not on npm. Everything below shipped in `0.4.293`.
+
 - **Extended** `verify:site` to the rendered head of every built page. `Base.astro` builds it once
   for all of them, which is exactly why a page that misses it misses it silently — nothing renders
   differently. Title, description, canonical and the two Open Graph tags are now required on all 27
@@ -214,6 +240,8 @@ defect; those are called out below.
 
 ## 0.4.290
 
+> **Never released.** This version was tagged and its publish run failed, so it is not on npm. Everything below shipped in `0.4.293`.
+
 - **Added** `npm run verify:site`, which checks what the site build produced rather than that it
   produced something. `llms.txt`, `llms-full.txt`, the markdown twin of every page, `robots.txt`
   and `api.json` are generated from the collection and nothing looked at the output — and each
@@ -227,6 +255,8 @@ defect; those are called out below.
 
 ## 0.4.289
 
+> **Never released.** This version was tagged and its publish run failed, so it is not on npm. Everything below shipped in `0.4.293`.
+
 - **Tested** `header/fields.ts` directly, the last source module no test imported. It is the sole
   owner of where each of the ten fixed fields lives and which diagnostic a field that fails its
   grammar deserves, and every function in it ran only as a step inside `parseHeader` — covered by
@@ -241,6 +271,8 @@ defect; those are called out below.
 
 ## 0.4.288
 
+> **Never released.** This version was tagged and its publish run failed, so it is not on npm. Everything below shipped in `0.4.293`.
+
 - **Tested** `options.ts` directly for the first time. It is 66 lines of Layer 1 whose whole job is
   refusing bad input, and no test imported it — every path through it ran only as a side effect of
   some larger read. Its own docblock records two misdiagnoses that reached users from a `NaN`
@@ -257,6 +289,8 @@ defect; those are called out below.
 
 ## 0.4.287
 
+> **Never released.** This version was tagged and its publish run failed, so it is not on npm. Everything below shipped in `0.4.293`.
+
 - **Added** a check on what `npm publish` would actually send. `publint` runs in CI and checks the
   manifest is well formed; it says nothing about membership, and membership is where the claims
   are — `tests/README.md` promises "nothing under `tests/` ever ships", and the fixture policy
@@ -902,6 +936,8 @@ defect; those are called out below.
 
 ## 0.4.242
 
+> **Never released.** This version was tagged and its publish run failed, so it is not on npm. Everything below shipped in `0.4.243`.
+
 - **Fixed** the link checker's own hand-written inventory, six releases after it was added to
   catch exactly that. 0.4.236 listed the site's standalone routes — `/`, `/demo`, `/llms.txt` and
   the rest — as a literal set, so deleting a route would have left the list vouching for it, and
@@ -914,6 +950,8 @@ defect; those are called out below.
 
 ## 0.4.241
 
+> **Never released.** This version was tagged and its publish run failed, so it is not on npm. Everything below shipped in `0.4.243`.
+
 - **Added** checks on `tests/README.md`, which described this suite with nothing checking that it
   still did. It is where the root README sends a contributor, and the fixture policy it states is
   the only reason six binary files are committed to a repository that otherwise builds every
@@ -982,6 +1020,8 @@ defect; those are called out below.
 
 ## 0.4.236
 
+> **Never released.** This version was tagged and its publish run failed, so it is not on npm. Everything below shipped in `0.4.237`.
+
 - **Added** a check that every internal link on the site points at something that exists. The
   documentation pages carry over a hundred `/docs/...` and `#anchor` links between them and
   nothing checked one: `astro check` validates types and content collections, not hrefs, and a
@@ -996,6 +1036,8 @@ defect; those are called out below.
 
 ## 0.4.235
 
+> **Never released.** This version was tagged and its publish run failed, so it is not on npm. Everything below shipped in `0.4.237`.
+
 - **Added** documentation for the three selection types, taking the recorded undocumented list
   from eleven to eight. `StreamSelection`, `EnvelopeSelection` and `TriggerSelection` are what
   `streamRecords`, `readEnvelope` and `readTriggers` take, and every page showed an object literal
@@ -1010,6 +1052,8 @@ defect; those are called out below.
 
 ## 0.4.234
 
+> **Never released.** This version was tagged and its publish run failed, so it is not on npm. Everything below shipped in `0.4.237`.
+
 - **Added** documentation for the three formatter options types, and took them off the recorded
   list of undocumented ones. `FormatHeaderOptions`, `FormatAnnotationsOptions` and
   `FormatReportOptions` are exported and every field of each was described somewhere in prose, but
@@ -1022,6 +1066,8 @@ defect; those are called out below.
 
 ## 0.4.233
 
+> **Never released.** This version was tagged and its publish run failed, so it is not on npm. Everything below shipped in `0.4.237`.
+
 - **Changed** the packaging checks to run on every push instead of only at publish time.
   `publint --strict` and `@arethetypeswrong/cli` are the two things `npm run check` cannot do —
   they read the manifest against the files npm would actually pack, and resolve each subpath the
@@ -1034,6 +1080,8 @@ defect; those are called out below.
 
 ## 0.4.232
 
+> **Never released.** This version was tagged and its publish run failed, so it is not on npm. Everything below shipped in `0.4.237`.
+
 - **Fixed** the site's version sweep reading only `.astro` files. `website/src/pages/` also holds
   seven `.ts` routes, and they emit prose exactly the way a component does: `llms.txt` is the map
   an agent is handed, `[...slug].md.ts` is the markdown twin of every documentation page, and
@@ -1046,6 +1094,8 @@ defect; those are called out below.
 
 ## 0.4.231
 
+> **Never released.** This version was tagged and its publish run failed, so it is not on npm. Everything below shipped in `0.4.237`.
+
 - **Fixed** four documentation sweeps reading a narrower set of pages than the site publishes.
   `docs-coverage.test.ts`, `diagnostic-docs.test.ts` and `readme-status.test.ts` — the last of
   them twice — each wrote its own reader, three globbing `content/docs/*.md` and one calling

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.4.306",
+  "version": "0.4.308",
   "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.306';
+export const VERSION = '0.4.308';