edfcore 0.4.328 → 0.4.330

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

package/docs/CHANGELOG.md

@@ -6,6 +6,29 @@ 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.330
+
+- **Added** a check over `migrating-to-0-3.md`, which was one of four documentation pages no test
+  named. It is a rename table and a `sed` recipe, and both can go stale in a way a reader cannot
+  detect: the table's three new names now have to be exports, and its three old names have to be
+  absent, because a barrel still carrying `sampleIndexAt` would let an unmigrated call site keep
+  working and make the whole page fiction.
+- The recipe is lifted out of the page's own fence and run. The page warns in the next paragraph
+  that `sampleStartTicks` is a prefix of `sampleStartTicksOf` and that a substring replace would
+  damage the second, so the `\b` anchors are load-bearing — and that is checked both ways: the
+  recipe leaves the longer name alone, and the same recipe without the anchors turns it into
+  `gridSampleStartTicksOf`, which is not a name this package has. Run as regexes rather than by
+  shelling out, since `sed -i` takes an argument on BSD and not on GNU.
+
+## 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

package/package.json

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