chore(deps): raise the Pi compatibility floor to 0.84.3 - #333
Closed
JS-banana wants to merge 1 commit into
Closed
Conversation
JS-banana
force-pushed
the
chore/pi-baseline-0.84.3
branch
from
September 1, 2026 07:57
c0bb556 to
c705e7c
Compare
This was referenced Sep 1, 2026
Author
|
#330 已支持,本 PR 关闭 |
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.
Problem
OpenPI documents and freezes Pi 0.84.1 even though provider correctness now depends on host contracts first released in Pi 0.84.3. Caret development ranges allow newer patches, but the frozen lock and existing CI lanes do not continuously prove either the intended floor or the newest locked patch.
Closes #328. This is the project-wide compatibility follow-up to #269; that provider PR intentionally keeps
package.jsonandbun.lockunchanged.Value
The repository gains one explicit, reviewable Pi support boundary instead of handling version-sensitive provider behavior case by case. Contributors test against the current compatible patch, while CI prevents accidental use of APIs newer than the documented minimum.
Approach
^0.84.1to^0.84.3and regeneratebun.lock, which currently resolves the compatible Pi family at 0.84.4.*; Pi remains the owner of the host packages used by installed OpenPI packages.Validation
NPM_CONFIG_REGISTRY=https://registry.npmjs.org bun install --frozen-lockfile— passed with locked Pi 0.84.4.bun run check— passed on locked Pi 0.84.4 and an isolated exact Pi 0.84.3 family.PI_CODING_AGENT_DIR="$(mktemp -d)" bun run test— both versions passed 1,115 of 1,116 Node tests with the single Windows-only test skipped, plus 30/30 Vitest tests.git diff --check— passed.Impact
Users and contributors must use Pi 0.84.3 or newer for the documented support boundary. No model-visible tools or context, runtime provider behavior, or persisted configuration/data change in this PR. The lockfile moves normal development to Pi 0.84.4 and its compatible transitive dependency graph; CI gains one full minimum-version lane and therefore additional runtime.