Changes in v0.0.13
Published v0.0.13 changes and their remaining compatibility and platform limits.
v0.0.13 was published on 2026-10-10 from commit a6e109b. This page records changes since v0.0.12. Check tapid --version and command help before execution; release availability does not establish platform acceptance or full npm compatibility.
Dependency operations
| Change | Documentation |
|---|---|
| Exact locked installation with downloads for missing verified trees | tapid ci |
| Matching-lock replay, compatible locked selections after manifest changes and frozen source hydration | tapid install |
| Offline import of the supported npm lockfile v3 subset | tapid import-package-lock |
| Versioned JSON outcomes for supported package commands | JSON results |
| Linking all discovered workspace members, member cycles and expanded acceptance checks | Upstream workspace contract |
| Exact approvals for dependency hooks and Linux ManagedTree execution | Dependency scripts |
| Preserve overlapping dependency sections during update | Change #254 |
Imported npm locks use schema 8 and their own frozen-install path. Approved derived outputs use schema 9. tapid ci, import and hook execution have different prerequisites; they are not interchangeable ways to install a project.
Contributor and release work
Repository tooling moved from Python to TypeScript. This changes engineering tools, not package ecosystem support. Release recovery smoke checks were restored, CodeQL name assertions were corrected, and v0.0.13 is now published. These engineering changes do not complete platform acceptance.
The tagged v0.0.13 notes currently summarize verified CI installs. The table above also covers published source changes that are not fully described in those notes.
No feature on this page establishes production support, complete npm compatibility or completion of platform acceptance. The hosted explorer and account application remain planned work.