pipework 0.42.0 → 0.43.0
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/CHANGELOG.md +4 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,9 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.43.0
|
|
4
|
+
|
|
5
|
+
- **`pnpm@10.33.0` is now the version pipework itself builds and tests on.** 0.41.0 made it the default written into a generated `package.json` while this repo still ran 9.15.4 — a default nothing exercised. The repo's own `packageManager` now matches, and the full gate (type-check, lint, boundaries, unit/contract, isolation) runs under pnpm 10. The lockfile is unchanged: pnpm 10 reads and writes the same `9.0` format, and no dependency needed a build-script allowance. Nothing about the generated output changed — this is the witness for the default 0.41.0 already ships.
|
|
6
|
+
|
|
3
7
|
## 0.42.0
|
|
4
8
|
|
|
5
9
|
- **Fix: `check`'s files-linted count now covers workspace-root files.** `runLint` iterated modules only, so a lintable file at the workspace root — outside every module — was never linted by `check` and never appeared in its count. The reading said "N files linted" over a population that silently excluded them, and the lint verdict for those files had to be produced outside pipework with a direct `eslint` run. Root files no module covers are now linted as their own pass and counted: `✓ Lint (2 modules + 3 root files)`, with the per-pass line naming them like any module's. Where eslint cannot reach them, the existing coverage refusal names each file and its reason instead of passing. Which files count as root sources follows `lint.include` (or `lint.modules["."].include`), defaulting to `src` as elsewhere.
|