edfcore 0.4.225 → 0.4.226
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 +10 -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.226";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,16 @@ 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.226
|
|
10
|
+
|
|
11
|
+
- **Added** a recovery message for the one release step the 0.4.200 revert cannot reach. By the
|
|
12
|
+
time `gh release create` runs, the bump is committed and the tag is pushed, so there is nothing
|
|
13
|
+
local to undo — and `publish.yml` triggers on a PUBLISHED release rather than on a tag, so a
|
|
14
|
+
failure there leaves a version that exists in git and never reaches npm. Nothing in the
|
|
15
|
+
repository would notice: `changelog-continuity.test.ts` checks this file against itself, and the
|
|
16
|
+
entry would be present and correct. The script now says how to finish the release, and warns that
|
|
17
|
+
re-running it would cut the next version and leave this one a hole.
|
|
18
|
+
|
|
9
19
|
## 0.4.225
|
|
10
20
|
|
|
11
21
|
- **Fixed** `npm run format` being unable to produce a tree `npm run lint` accepts. `format` was
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED