edfcore 0.4.294 → 0.4.295
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 +9 -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.295";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,15 @@ 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.295
|
|
10
|
+
|
|
11
|
+
- **Corrected** the release script's closing message, which 0.4.294 made false one release ago. It
|
|
12
|
+
said "publish.yml is now running and will publish to npm" and offered `npm view edfcore version`
|
|
13
|
+
to confirm — advice from when the script exited before the publish began. It now waits for that
|
|
14
|
+
publish, so by the time those lines print the version is already installable. It says so, and
|
|
15
|
+
gives the install command and the release URL instead of two ways to check something already
|
|
16
|
+
known.
|
|
17
|
+
|
|
9
18
|
## 0.4.294
|
|
10
19
|
|
|
11
20
|
- **Added** the last wait the release was missing: whether the version actually reached npm. The
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED