edfcore 0.4.200 → 0.4.201
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 +7 -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.201";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,13 @@ 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.201
|
|
10
|
+
|
|
11
|
+
- **Fixed** the half of 0.4.200 it left out. The lockfile sync runs after the bump and before the
|
|
12
|
+
checks, so it sat outside the `try` that puts the version back — and it is the step most likely
|
|
13
|
+
to fail for a reason unrelated to the code, since it reaches the registry. A failed `npm install
|
|
14
|
+
--package-lock-only` would still have consumed the number.
|
|
15
|
+
|
|
9
16
|
## 0.4.200
|
|
10
17
|
|
|
11
18
|
- **Fixed** `scripts/release.mjs` consuming a version number when its own checks fail. The bump is
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED