Files
hyperframes/packages
Vance Ingalls df1d20b765 fix(cli): check buildId when resolving the managed Chrome cache
Address the highest-severity max-effort code-review finding on the now-
merged #2082 (the drawElement Chrome-version-pin fix): findFromHyperframesCache
matched a cached Chrome by browser type only, never comparing its
buildId against CHROME_VERSION. Any machine that already rendered with
an older hyperframes version has an old build (this pin has moved
131 -> 151 -> 152 across releases) sitting in ~/.cache/hyperframes/chrome,
which satisfied the lookup and silently defeated the whole point of
#2082's version bump for exactly the population it was meant to fix —
drawElement's new capability probe would then permanently and silently
fall back to screenshot capture instead of ever fetching a build that
implements canvas.drawElementImage.

Verified directly (not just via review): seeded ~/.cache/hyperframes/chrome
with the old 131 build, confirmed a real render previously kept using it
forever; with this fix it's correctly ignored and 152 is downloaded.
New regression test locks in the buildId mismatch case.
2026-07-08 16:10:43 -07:00
..
2026-07-08 15:51:39 -07:00
2026-07-08 15:51:39 -07:00
2026-07-08 15:51:39 -07:00
2026-07-08 15:51:39 -07:00
2026-07-08 15:51:39 -07:00
2026-07-08 15:51:39 -07:00
2026-07-08 15:51:39 -07:00
2026-06-16 13:16:09 -04:00
2026-07-08 15:51:39 -07:00
2026-07-08 15:51:39 -07:00
2026-07-08 15:51:39 -07:00