edfcore 0.4.283 → 0.4.284
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 +15 -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.284";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,21 @@ 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.284
|
|
10
|
+
|
|
11
|
+
- **Added** a check that the README's first badge and `/api.json` are the same contract. The badge
|
|
12
|
+
URL carries a JSONPath — `query=%24.exports.total` — against an endpoint generated from the three
|
|
13
|
+
built entry points, and that design exists so the number is counted rather than typed: the site
|
|
14
|
+
footer read "Version 0.1.0" for three minor series. The two halves had never been compared.
|
|
15
|
+
Renaming `total` in the endpoint leaves the badge querying a path that is gone, and shields.io
|
|
16
|
+
does not fail loudly for that — it renders an empty value in the corner of the README, which is
|
|
17
|
+
the one place nobody looks after the first week.
|
|
18
|
+
- The path is extracted from the badge and walked through the object the endpoint builds, the URL
|
|
19
|
+
is checked against `package.json`'s `homepage`, and the total is checked against the API surface
|
|
20
|
+
row it should agree with. The endpoint is read as text rather than imported, because it lives
|
|
21
|
+
under `website/` and importing it would pull in a tsconfig CI does not install — the boundary
|
|
22
|
+
0.4.264 exists to hold.
|
|
23
|
+
|
|
9
24
|
## 0.4.283
|
|
10
25
|
|
|
11
26
|
- **Added** a check that the sidebar order is a total order. `content.config.ts` requires `section`
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED