chore(sdk): adopt Pi SDK 0.83.0 - #113
Draft
github-actions[bot] wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated Pi SDK watch. A new
@earendil-works/pi-coding-agentrelease is outside the tested range.0.80 0.82What this PR changes
@earendil-works/pi-coding-agent,@earendil-works/pi-tui) used for typecheck + tests0.83toPLANNER_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 requiredpi.*/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.