edfcore 0.4.195 → 0.4.197
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.
- package/dist/constants.d.ts +1 -1
- package/dist/constants.js +1 -1
- package/docs/CHANGELOG.md +15 -0
- package/package.json +1 -1
- package/src/constants.ts +1 -1
package/dist/constants.d.ts
CHANGED
|
@@ -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.
|
|
112
|
+
export declare const VERSION = "0.4.197";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
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.197
|
|
10
|
+
|
|
11
|
+
- **Corrected** the consumed-version count in `scripts/release.mjs`, which had drifted in the file
|
|
12
|
+
written to stop exactly this. Its note said the failure "has happened twice" and named two; the
|
|
13
|
+
error message it prints named three. It has happened four times, and 0.4.176 was in neither list —
|
|
14
|
+
so the guidance handed to the next person to lose a number omitted the most recent one to be lost.
|
|
15
|
+
|
|
16
|
+
## 0.4.196
|
|
17
|
+
|
|
18
|
+
- **Added** the guard for 0.4.194: the changelog's version headings must descend without repeating
|
|
19
|
+
and skip no number, so a run that consumes one has to be written down rather than leaving a hole
|
|
20
|
+
a reader cannot interpret. Checked against the file alone, not `git tag` — CI checks out at depth
|
|
21
|
+
1 and fetches no tags, so a tag-based version would find none and pass while asserting nothing.
|
|
22
|
+
Removing the 0.2.29 entry fails it with `0.2.28 -> 0.2.30`.
|
|
23
|
+
|
|
9
24
|
## 0.4.195
|
|
10
25
|
|
|
11
26
|
- **Recorded** why `v0.1.1` has no tag, the last unexplained hole in the version history. It is not
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED