edfcore 0.4.327 → 0.4.329

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

package/docs/CHANGELOG.md

@@ -6,6 +6,27 @@ 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.329
+
+- **Added** `--through` to `npm run announce`, which closes a batch at a version that is not the
+  newest tag. A batch is what was asked for rather than what happens to be tagged, so two of them
+  can be in flight at once — and without this the only expressible range ended at the newest tag,
+  so announcing an older batch would have swallowed the newer one.
+- It refuses a version that has no tag rather than announcing an empty or a wrong range, and the
+  default is unchanged: everything since the last release.
+
+## 0.4.328
+
+- **Added** a guard for the release model 0.4.327 introduced. Three files describe it and none of
+  them enforced it, and the dangerous edit is small and looks like a revert: putting `release:
+  types: [published]` back on `publish.yml` leaves every test green, every workflow valid, and
+  `scripts/release.mjs` pushing tags that trigger nothing.
+- That is not hypothetical. It is exactly how 0.4.287 through 0.4.292 were lost — six versions
+  tagged, six green CI runs, nothing on npm, found only by looking at the registry. So the trigger
+  is asserted from the outside, along with the two orderings the gate depends on: that `ci.yml`
+  still runs on a push to main, since the release polls for check runs that would otherwise never
+  register, and that `release.mjs` pushes main before it tags rather than after.
+
 ## 0.4.327
 
 - **Changed** how publishing is triggered: `publish.yml` now runs on a pushed **tag** rather than

package/package.json

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