Evidence record / heypi

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-13-heypi-pi-1-x-does-not-reach-heypi-s-0-79-x-dependency-range

Pi 1.x does not reach heypi’s 0.79.x dependency range. Pi shipped 1.0.0 and 1.2.0 in the window without an accompanying heypi release. heypi 0.3.0-beta.2 declares >=0.79.6 <0.80.0; its repository lockfile and an ordinary fresh resolution select 0.79.10. Existing consumer lockfiles can retain another allowed 0.79.x version. Pi 0.79.10 declares Node >=22.19.0 in its registry record and published package.json, so the core’s own Node >=22 declaration is not the complete fresh dependency requirement. The lockfile establishes resolution, not a successful compatibility test. Pi 0.80.8 documents removal of AuthStorage and replacement of authStorage/modelRegistry session options with modelRuntime. The checked 0.80.8 and 1.2.0 exports cannot satisfy heypi’s named ESM import. heypi’s re-exported tool/extension APIs also come from its embedded Pi line. The four published Pi advisory ranges checked by the verifier exclude 0.79.10; that is not a complete transitive vulnerability assessment.

Channel: tagged-release upstream; embedded heypi preview-or-beta. Half: both. Date: 2026-10-01 (Pi 1.0.0); Pi 1.2.0 published 2026-10-12.

Operator consequence: The old profile’s claim that Pi breaking changes automatically reach heypi was backwards for normal npm resolution. The narrow range blocks both those releases and their improvements. Do not lift Pi to 1.2.0 with an override: the checked exports would fail ESM linking, and session construction needs a port. Use the API of the Pi version actually resolved, and assess ecosystem extension compatibility individually. A heypi release porting the imports and session API would settle the integration gap; no runtime compatibility test was run here.

Receipt

Finding metadata

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-heypi-pi-1-x-does-not-reach-heypi-s-0-79-x-dependency-range

Profile citations

  • heypi / claim / pi-range-stays-on-0-79
  • heypi / claim / resolved-pi-node-minimum
  • heypi / posture / capability

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact