edfcore 0.4.328 → 0.4.329
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.329";
|
|
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.329
|
|
10
|
+
|
|
11
|
+
- **Added** `--through` to `npm run announce`, which closes a batch at a version that is not the
|
|
12
|
+
newest tag. A batch is what was asked for rather than what happens to be tagged, so two of them
|
|
13
|
+
can be in flight at once — and without this the only expressible range ended at the newest tag,
|
|
14
|
+
so announcing an older batch would have swallowed the newer one.
|
|
15
|
+
- It refuses a version that has no tag rather than announcing an empty or a wrong range, and the
|
|
16
|
+
default is unchanged: everything since the last release.
|
|
17
|
+
|
|
9
18
|
## 0.4.328
|
|
10
19
|
|
|
11
20
|
- **Added** a guard for the release model 0.4.327 introduced. Three files describe it and none of
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED