fix(ci): cap broken AI SDK v6 patches - #2141
Merged
Merged
Conversation
|
agents
@cloudflare/ai-chat
@cloudflare/codemode
hono-agents
@cloudflare/shell
@cloudflare/think
@cloudflare/voice
@cloudflare/worker-bundler
commit: |
cjol
approved these changes
Aug 24, 2026
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.
Summary
Temporarily cap the AI SDK v6 compatibility lane at the last known-good patch:
This changes only the throwaway dependency range written by
scripts/use-ai-sdk-major.mjs. Published peer ranges and the repository lockfile are unchanged.Why
The compatibility workflow uses
pnpm install --no-frozen-lockfile, soai@^6.0.0began resolving newly published patches during existing PR runs.Observed behavior:
ai@6.0.259: Think Workers 886/886ai@6.0.260: 16 deterministic failures in client-tool and HITL testsai@6.0.261: same 16 failuresai@6.0.263: same 16 failuresThe failure reproduces on current
main, so it is not caused by the PR that first exposed it. The affected tool results remain atinput-available, and RPC client-tool executors are not invoked.The cap keeps testing the supported v6 line without silently dropping AI v6 coverage. It should be removed or advanced when an upstream patch restores the affected behavior.
Verification
aidependency to>=6.0.0 <6.0.260ai@6.0.259git diff --checkpass