edfcore 0.4.211 → 0.4.213
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 +17 -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.213";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,23 @@ 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.213
|
|
10
|
+
|
|
11
|
+
- **Fixed** the guard added in 0.4.205, which was the shape of the defect it catches. It compared
|
|
12
|
+
the section list in three consumer files against the schema — and named those three by hand, so a
|
|
13
|
+
fourth file writing the list out again would not have been one of them and the run would have
|
|
14
|
+
stayed green while the new copy drifted. It now finds every file under `website/src` that
|
|
15
|
+
declares `SECTIONS`. This is the third guard in three batches that turned out narrower than the
|
|
16
|
+
claim it guards.
|
|
17
|
+
|
|
18
|
+
## 0.4.212
|
|
19
|
+
|
|
20
|
+
- **Added** the guard for 0.4.211, and the counterpart to 0.4.210 on the other side of the repo:
|
|
21
|
+
`npm --prefix website run check` now passes `--minimumFailingSeverity hint`, so the site's type
|
|
22
|
+
check fails on a hint instead of printing one and exiting 0. That is how the JSON-LD hint rode
|
|
23
|
+
along in CI for as long as it did. Both halves of the repository now fail on the quietest thing
|
|
24
|
+
their checkers can say.
|
|
25
|
+
|
|
9
26
|
## 0.4.211
|
|
10
27
|
|
|
11
28
|
- **Added** `is:inline` to the JSON-LD block in `Base.astro`, clearing the one hint `astro check`
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED