edfcore 0.4.478 → 0.4.480
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 +35 -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.480";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,41 @@ 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.480
|
|
10
|
+
|
|
11
|
+
- **Added** membership checks inside the two directories the package actually ships.
|
|
12
|
+
`verify:tarball` asked which directories reached the tarball and never asked what was in them —
|
|
13
|
+
and `files` is an allow-list of DIRECTORIES, so `src` ships whatever happens to be sitting in
|
|
14
|
+
it, tracked or not.
|
|
15
|
+
- A half-finished module kept while refactoring, a `.orig` left by a merge, an editor's swap file:
|
|
16
|
+
each goes out to every consumer, and a published version is immutable. `src/` ships for exactly
|
|
17
|
+
one reason — the sourcemaps resolve into it — so `git ls-files src` is the right comparison: a
|
|
18
|
+
file git does not track is a file no map points at.
|
|
19
|
+
- `dist/` is checked the same way, against the three extensions `tsc` emits, so anything that
|
|
20
|
+
arrived there by some other route is named rather than shipped.
|
|
21
|
+
- Both fire on a stray file and both name it. The rules npm applies on its own are why this is
|
|
22
|
+
worth stating rather than assuming: `.DS_Store` is dropped by a convention this repository does
|
|
23
|
+
not write down and cannot see, the same class of invisible rule as the three files npm adds for
|
|
24
|
+
free just above the new check.
|
|
25
|
+
|
|
26
|
+
## 0.4.479
|
|
27
|
+
|
|
28
|
+
- **Fixed** a check that could pass on the machine that broke it and fail on CI. `file-references`
|
|
29
|
+
resolves a backticked path against every file in the working tree, and its skip list held
|
|
30
|
+
`scratch` but not `deleted` — both gitignored, both present only on the machine that put them
|
|
31
|
+
there.
|
|
32
|
+
- Found by hitting it. Retiring the badge-contract file to `deleted/` in 0.4.478 left a changelog
|
|
33
|
+
entry naming it; the reference resolved here and dangled on a clean checkout, so all three Node
|
|
34
|
+
jobs failed on the commit that retired the file — the moment its author is least expecting a
|
|
35
|
+
reference to it to break.
|
|
36
|
+
- The asymmetry is what made it easy to miss. The second walk in that file descends only `src`,
|
|
37
|
+
`tests`, `scripts` and `config`, so a retired file can never MAKE a claim; it could only ever
|
|
38
|
+
vouch for one.
|
|
39
|
+
- The walk is now a named function taking a root, and the new case runs it on a temporary tree
|
|
40
|
+
holding one live file, one under `deleted/` and one under `scratch/`. On the real tree the
|
|
41
|
+
assertion would say nothing on CI, where neither directory exists — which is the same trap one
|
|
42
|
+
level up.
|
|
43
|
+
|
|
9
44
|
## 0.4.478
|
|
10
45
|
|
|
11
46
|
- **Removed** the `exports` badge from the top of the README, at the user's request. The number it
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED