edfcore 0.4.6 → 0.4.7
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.7";
|
|
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.7
|
|
10
|
+
|
|
11
|
+
- **Fixed** `publish.yml`'s `permissions` comment claiming `id-token: write` is for trusted
|
|
12
|
+
publishing and that "no long-lived secret is stored anywhere". The publish step in the same file
|
|
13
|
+
says the opposite: trusted publishing 400s here, and NPM_TOKEN is the credential. The permission
|
|
14
|
+
is for the provenance attestation, which is the one claim that survived.
|
|
15
|
+
|
|
9
16
|
## 0.4.6
|
|
10
17
|
|
|
11
18
|
- **Fixed** the drift-recovery note in `scripts/release.mjs` telling you to run
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED