Skip to content

chore(sdk): adopt Pi SDK 0.84.2 - #115

Draft
github-actions[bot] wants to merge 1 commit into
mainfrom
sdk-watch
Draft

chore(sdk): adopt Pi SDK 0.84.2#115
github-actions[bot] wants to merge 1 commit into
mainfrom
sdk-watch

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Automated Pi SDK watch. A new @earendil-works/pi-coding-agent release is outside the tested range.

  • latest: 0.84.2 · known-good: 0.80 0.82 0.83
  • typecheck + tests PASS against 0.84.2 — likely a safe adoption.

What this PR changes

  • bumps the devDependency pins (@earendil-works/pi-coding-agent, @earendil-works/pi-tui) used for typecheck + tests
  • appends 0.84 to PLANNER_KNOWN_GOOD_PI_VERSIONS (existing lines stay validated)

Before merging review the SDK surface probe in src/runtime/sdk-compat.ts (SDK_REQUIRED_SURFACES). If the check above failed, a required pi.* / ctx.* surface moved — fix the call sites, not just the pins.

The failure blurb above is a fixed template, not a diagnosis: check what actually failed. npm run build (tsc against the real typings) is the signal that a surface moved; a red test alone may just be a fixture coupled to something this PR rewrote.

Self-rewriting: while this branch has only bot commits, each run force-pushes it (bumping to the newest SDK), so there is only ever this one PR. The moment you push a commit here, the watcher stands down and never touches your work — merge or close the PR to let it resume. It also closes automatically if the SDK returns to the known-good range.

@github-actions
github-actions Bot force-pushed the sdk-watch branch 7 times, most recently from a2d4918 to 4d62bf7 Compare August 14, 2026 07:52
@github-actions github-actions Bot changed the title chore(sdk): adopt Pi SDK 0.84.1 chore(sdk): adopt Pi SDK 0.84.2 Aug 15, 2026
@github-actions
github-actions Bot force-pushed the sdk-watch branch 7 times, most recently from 79ee945 to 422ccde Compare August 21, 2026 07:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants