edfcore 0.4.203 → 0.4.204
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.204";
|
|
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.204
|
|
10
|
+
|
|
11
|
+
- **Corrected** the reason `publish.yml` pins npm. The step said trusted publishing needs
|
|
12
|
+
>= 11.5.1, which was true when f363feb added it on 2026-08-01 — but ed89f67 moved the workflow
|
|
13
|
+
to a granular access token two days later, and the note further down the same file now explains
|
|
14
|
+
that registering trusted publishing returns 400 for this package. One comment justified the step
|
|
15
|
+
by a mechanism another said was unavailable. The pin still earns its place; the reason is now
|
|
16
|
+
the one that applies.
|
|
17
|
+
|
|
9
18
|
## 0.4.203
|
|
10
19
|
|
|
11
20
|
- **Corrected** the docblock of `changelog-continuity.test.ts`, which had gone stale twice over. It
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED