chore: update dependencies#5079
Conversation
Bumps every workspace package's dependencies via taze (root, packages, examples, templates), re-pins Expo SDK packages with expo install --fix, and regenerates pnpm-lock.yaml. Pins the @earendil-works/pi-* family (pi-coding-agent, pi-agent-core, pi-ai, pi-tui) to 0.80.7 via pnpm-workspace.yaml overrides: 0.80.10 drops the AuthStorage export react-pi's ThreadSupervisor imports and the registerOAuthProvider/resetOAuthProviders exports pi-coding-agent's own model-registry imports, breaking the build. Verified: full build (except apps/social-media, blocked by this sandbox's network policy for cdn.jsdelivr.net, unrelated to deps), lint, and turbo test all pass. pnpm test:types has 8 pre-existing failures that are byte-identical before and after this change (confirmed via a stash-and-diff against the base branch), so none are new regressions. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DyAMgB68QuKuLcuRaDYDo6
🦋 Changeset detectedLatest commit: 5d7132d The changes in this PR will be included in the next version bump. This PR includes changesets to release 19 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Reviews (1): Last reviewed commit: "chore: update dependencies" | Re-trigger Greptile |
| "@ai-sdk/react-v3": "npm:@ai-sdk/react@^4.0.34", | ||
| "@assistant-ui/x-buildutils": "workspace:*", | ||
| "@testing-library/dom": "^10.4.1", |
There was a problem hiding this comment.
Legacy Compatibility Leg Moves Forward
@ai-sdk/react-v3 now installs React SDK v4 and ai-v6 now installs AI SDK v7. The cloud package still supports and tests its older peer-dependency leg, so CI will exercise the newer APIs twice while no longer detecting a regression for consumers using AI SDK v6 / React SDK v3.
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
There was a problem hiding this comment.
1 issue found across 69 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="packages/x-buildutils/package.json">
<violation number="1" location="packages/x-buildutils/package.json:27">
P2: Build-tool installation is no longer supported on Node 24.0–24.10, despite the workspace declaring Node `>=24`; those versions now hit the Babel engine constraint (and `tsdown@0.22.11` has the same floor). The declared engine floor could be raised to `>=24.11.0`, or the build-tool dependency set could remain compatible with all declared Node 24 versions.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
| "sideEffects": false, | ||
| "dependencies": { | ||
| "@babel/core": "^7.29.7", | ||
| "@babel/core": "^8.0.1", |
There was a problem hiding this comment.
P2: Build-tool installation is no longer supported on Node 24.0–24.10, despite the workspace declaring Node >=24; those versions now hit the Babel engine constraint (and tsdown@0.22.11 has the same floor). The declared engine floor could be raised to >=24.11.0, or the build-tool dependency set could remain compatible with all declared Node 24 versions.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At packages/x-buildutils/package.json, line 27:
<comment>Build-tool installation is no longer supported on Node 24.0–24.10, despite the workspace declaring Node `>=24`; those versions now hit the Babel engine constraint (and `tsdown@0.22.11` has the same floor). The declared engine floor could be raised to `>=24.11.0`, or the build-tool dependency set could remain compatible with all declared Node 24 versions.</comment>
<file context>
@@ -24,12 +24,12 @@
"sideEffects": false,
"dependencies": {
- "@babel/core": "^7.29.7",
+ "@babel/core": "^8.0.1",
"@tsconfig/strictest": "^2.0.8",
"babel-plugin-react-compiler": "^1.0.0",
</file context>
Automated review (cubic-dev-ai, greptile) caught several taze bumps that silently crossed version boundaries this dependency chore shouldn't: - @babel/core ^7.29.7 -> ^8.0.1 in x-buildutils is a Babel major the installed babel-plugin-react-compiler@1.0.0 doesn't support (it still depends on @babel/types@^7.26.0), and broke `pnpm check:resource-memo` (8 resource-hosting functions bailed out of the compiler). Reverted to 7.x. - cloud-ai-sdk's @ai-sdk/react-v3 and ai-v6 devDependency aliases exist to exercise the older leg of this package's peer-dependency union (^3.0.0 || ^4.0.0 and ^6.0.0 || ^7.0.0). taze bumped both aliases past their pinned major, so test:peer-v6 was silently testing v4/v7 instead of v3/v6. Reverted to the pinned majors. - react-lexical's lexical/@lexical/react/@lexical/utils moved from the 0.47 line to 0.48 (a major-equivalent bump for a pre-1.0 runtime-value dependency) inside a routine patch changeset, which AGENTS.md's upstream-majors doctrine reserves for a dedicated major PR. Reverted to 0.47. - eve's devDependency test pin and the with-eve/templates/eve example dependency moved to 0.25.3 while the published peerDependencies floor stayed at ^0.24.3, so consumers on eve 0.25.x would see an unmet peer. Reverted to ^0.24.3 to keep the tested and advertised versions aligned. - Added @earendil-works/pi-coding-agent to the pnpm-workspace.yaml overrides alongside pi-agent-core/pi-ai/pi-tui, so a future caret dependency on it can't drift off 0.80.7 the way the others could. Verified: full build, lint, check:resource-memo, and turbo test all pass; cloud-ai-sdk's test:v7/test:peer-v6/test:types:peer-v6 all pass against the correct majors. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DyAMgB68QuKuLcuRaDYDo6
|
"Test Changed Packages" failed on This is a pre-existing race in the CI job, not caused by this PR's dependency changes. I don't have permission to re-run the failed job from here. Could a maintainer re-run "Test Changed Packages"? Fixing the underlying missing turbo dependency edge is a separate concern from this dependency-update PR and probably deserves its own issue/PR. Generated by Claude Code |
Summary
update-depsskill: bumps every workspace package's dependencies viataze major -f -w -r(root,packages/*,examples/*,templates/*,apps/*), re-pinsexamples/with-expoto the SDK 57 line withexpo install --fix, and regeneratespnpm-lock.yamlfrom scratch.@earendil-works/pi-*family (pi-coding-agent,pi-agent-core,pi-ai,pi-tui) to0.80.7via a newoverridesblock inpnpm-workspace.yaml.0.80.10drops theAuthStorageexport that@assistant-ui/react-pi'sThreadSupervisor.tsimports, and theregisterOAuthProvider/resetOAuthProvidersexports thatpi-coding-agent's ownmodel-registry.tsimports — both break the build. Since these packages release in lockstep and reference each other with wide^0.80.xranges, pinning only the top-levelpi-coding-agentdependency wasn't enough; the whole family needed the override.patchfor every published package whosepackage.jsonchanged) viascripts/generate-deps-changeset.sh.Test plan
pnpm build— all 84 buildable workspace tasks pass.apps/social-mediais excluded: its build fetches fonts fromcdn.jsdelivr.net, which this sandbox's network policy blocks; unrelated to this change.pnpm lint— passes (oxlint + oxfmt), no new warnings.turbo test— all 74 test tasks pass. A first full-concurrency run showed 4 timeouts inpackages/cli's subprocess-spawning tests; re-running in isolation and at--concurrency=4showed these were CPU-contention flakes in this 4-core sandbox, not real failures.pnpm test:types— 8 packages failtsc --noEmit. Verified viagit stash+ reinstalling the pre-update lockfile that these are pre-existing failures onmain, byte-identical before and after this change — none are new regressions from the dependency bump.🤖 Generated with Claude Code
https://claude.ai/code/session_01DyAMgB68QuKuLcuRaDYDo6
Generated by Claude Code