pi-crew 0.9.30 → 0.9.32
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 +28 -0
- package/dist/build-meta.json +187 -153
- package/dist/index.mjs +1346 -1276
- package/dist/index.mjs.map +4 -4
- package/package.json +3 -2
- package/src/extension/register.ts +3 -0
- package/src/runtime/team-runner.ts +36 -4
- package/src/state/state-store.ts +9 -3
- package/src/ui/run-dashboard.ts +25 -10
- package/src/workflows/cost-estimator.ts +34 -0
- package/src/workflows/validate-workflow.ts +10 -0
- package/tsconfig.json +3 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,33 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## [0.9.32] — typescript 7 upgrade (2026-07-10)
|
|
4
|
+
|
|
5
|
+
Upgraded the TypeScript toolchain from 5.9.3 to **7.0.2** (the native Go port, a.k.a. Project Corsa / `typescript-go`). This is a dev-toolchain-only change: pi-crew ships source `.ts` loaded at runtime via Node `--experimental-strip-types`, so end users see zero behavioral change. The upgrade affects only `npm run typecheck` and editor type-checking.
|
|
6
|
+
|
|
7
|
+
### Performance
|
|
8
|
+
- **`tsc --noEmit` is ~3x faster on pi-crew**: 40.0s → 13.1s (1112 `.ts` files). TS 7.0's native port reports 8–12x on larger codebases; pi-crew is below that curve due to its smaller file count.
|
|
9
|
+
|
|
10
|
+
### Changed
|
|
11
|
+
- **`typescript`**: `^5.9.3` → `^7.0.2` (native Go port; programmatic API removed in 7.0 — pi-crew has zero programmatic TS consumers, so no impact).
|
|
12
|
+
- **`@types/node`**: promoted from transitive (via `@anthropic-ai/sdk` peer) to direct `devDependency` (`^25.9.5`) so an upstream peer bump can no longer blackhole pi-crew's types.
|
|
13
|
+
- **`tsconfig.json`**: pinned two flags explicitly that became TS 6.0 defaults (inherited by 7.0):
|
|
14
|
+
- `"verbatimModuleSyntax": true`
|
|
15
|
+
- `"noUncheckedSideEffectImports": true`
|
|
16
|
+
|
|
17
|
+
### Fixed (test accompaniments to the TS 7 breaking changes)
|
|
18
|
+
- **`test/unit/export-adapters.test.ts`**: replaced the bare side-effect import `import "../../src/adapters/index.ts";` with a bound import `import { adapterRegistry } from "../../src/adapters/index.ts";`. Required by `noUncheckedSideEffectImports: true` (the import is intentional — it triggers `adapterRegistry.register()` at module load — so the binding is unused but the side effect still runs).
|
|
19
|
+
- **`test/unit/dwf-authoring-types.test.ts`**: added `--ignoreConfig` to the spawned `tsc` invocation. TS 7.0 introduced a breaking change (TS5112): command-line builds that pass a file path now error when a `tsconfig.json` exists in the cwd, unless `--ignoreConfig` is passed. This compile-check test supplies its own flags and intentionally ignores the repo's tsconfig.
|
|
20
|
+
|
|
21
|
+
### Notes
|
|
22
|
+
- **TS 6.0 was skipped** (released 2026-03-23; pi-crew jumped 5.9.3 → 7.0.2). TS 7.0 is typecheck-compatible with TS 6.0; the breaking-change matrix was audited in `research-typescript-v7-upgrade.md` and pi-crew was already compliant on every inherited default.
|
|
23
|
+
- **`dist/` staleness** (pre-existing on `main`, unrelated to this upgrade) was left untouched in this PR. GitHub CI excludes the mtime-based `check:bundle-staleness` check.
|
|
24
|
+
|
|
25
|
+
### Verification
|
|
26
|
+
- `tsc --noEmit`: 0 errors (independently re-verified).
|
|
27
|
+
- `biome lint` + `format:check`: clean (1123 files).
|
|
28
|
+
- Unit tests: passing, including the two TS-7-affected tests (`dwf-authoring-types`, `event-log-async`).
|
|
29
|
+
- Full risk analysis + decision matrix: `research-typescript-v7-upgrade.md`.
|
|
30
|
+
|
|
3
31
|
## [0.9.30] — observability hardening + steering injection guards (2026-07-10)
|
|
4
32
|
|
|
5
33
|
Cold-verified review of 12 findings across security, code quality, and explorer passes yielded 11 confirmed bugs (1 NOT-A-BUG). This release ships 9 of those fixes; the remaining 2 are documented as deferred follow-ups.
|