Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -182,7 +182,7 @@
"@types/uuid": "^11.0.0",
"@uiw/react-markdown-preview": "^5.1.5",
"@xyflow/react": "^12.9.2",
"ai": "~6.0.208",
"ai": "~7.0.44",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Commit the updated Bun lockfile

I checked .github/workflows/ci.yml:37 and .github/workflows/sdk-version-guard.yml:85; both install with bun install --frozen-lockfile, but this manifest now asks for ai@~7.0.44 while bun.lock still records the root dependency/override and resolved package as ai@~6.0.208. In any CI or local E2E path that uses the frozen lockfile, Bun must change the lockfile to satisfy this package.json change and will reject the install, so the SDK bump cannot build/test until the regenerated bun.lock is committed alongside it.

Useful? React with 👍 / 👎.

"argon2": "^0.45.1",
"aws-amplify": "^6.16.0",
"aws-jwt-verify": "^5.1.1",
Expand Down Expand Up @@ -307,7 +307,7 @@
"openai": {
"zod": "^4.1.11"
},
"ai": "~6.0.208",
"ai": "~7.0.44",
"@ai-sdk/provider": "~3.0.10",
"@ai-sdk/provider-utils": "~4.0.30",
"@ai-sdk/react": "~3.0.210",
Expand Down
Loading