edfcore 0.4.364 → 0.4.366
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 +31 -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.366";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,37 @@ 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.366
|
|
10
|
+
|
|
11
|
+
- **Added** a check that every version number this repository cites is one it released. The
|
|
12
|
+
codebase explains itself in release numbers — docblocks say "fixed in 0.3.56", the documentation
|
|
13
|
+
pages date every behaviour they describe, the changelog cross-references itself — and there are
|
|
14
|
+
several hundred such citations across 248 files, none of which had ever been checked.
|
|
15
|
+
- They rot silently in two directions: a transposed digit points a reader at nothing, and a
|
|
16
|
+
citation written while a version is still being cut names a number that never shipped, which is
|
|
17
|
+
the same failure the fourteen changelog holes were. A wrong version number looks exactly like a
|
|
18
|
+
right one to a compiler, a linter and a human skimming a diff.
|
|
19
|
+
- The hard part is telling a version from everything else shaped like one, since this tree is full
|
|
20
|
+
of EDF startdates and starttimes, spec clauses like `2.1.1` and runtime floors like `22.12.0`. A
|
|
21
|
+
loose scan reports forty-five of those and no real defects; `0.` with no leading zero separates
|
|
22
|
+
them exactly, and that narrowing is asserted against the lookalikes rather than left to luck.
|
|
23
|
+
|
|
24
|
+
## 0.4.365
|
|
25
|
+
|
|
26
|
+
- **Added** a check that the layer table in `AGENTS.md` names the modules that are actually at each
|
|
27
|
+
layer. `module-layers.test.ts` already enforces that every module declares a layer, that no
|
|
28
|
+
runtime import goes up one, and that the table names every layer the source declares — but not
|
|
29
|
+
the contents of any row.
|
|
30
|
+
- AGENTS.md calls the table "a summary of it, not a second definition", and a summary that
|
|
31
|
+
disagrees with its source is still wrong. This one is easy to disagree with, because two rows
|
|
32
|
+
split a directory: layer 5 is `io/` and layer 6 carves `io/read.ts` back out, exactly as layers 1
|
|
33
|
+
and 3 split `tal/`. So a directory claims everything under it except what another row names by
|
|
34
|
+
file, and both splits are asserted as the point of the rule rather than exceptions to it.
|
|
35
|
+
- Row 7 names nothing — "entry points, and the pure helpers over them" — which supplies the
|
|
36
|
+
closure that makes the check tight: every module no row claims has to be at layer 7. Only a path
|
|
37
|
+
counts as a claim, since row 5 also mentions `ByteSource`, which is the type the adapters
|
|
38
|
+
implement rather than a module being placed.
|
|
39
|
+
|
|
9
40
|
## 0.4.364
|
|
10
41
|
|
|
11
42
|
- **Added** checks for three claims in the README's "Design in one page", each of which is an
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED