edfcore 0.4.210 → 0.4.211
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.211";
|
|
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.211
|
|
10
|
+
|
|
11
|
+
- **Added** `is:inline` to the JSON-LD block in `Base.astro`, clearing the one hint `astro check`
|
|
12
|
+
has been printing. Without it the tag goes through Astro's script processing, which is for code
|
|
13
|
+
it is asked to bundle rather than for a literal payload that must reach the page exactly as
|
|
14
|
+
written — and this one is hand-escaped, so passing it through anything is the wrong default.
|
|
15
|
+
`astro check` now reports 0 errors, 0 warnings and 0 hints; the built `index.html` carries the
|
|
16
|
+
same graph it did before.
|
|
17
|
+
|
|
9
18
|
## 0.4.210
|
|
10
19
|
|
|
11
20
|
- **Added** the guard for 0.4.208 and 0.4.209: `npm run lint` now passes `--error-on-warnings`, so
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED