Repository navigation
chore: bump ai sdk family to ai 7.0.142, effect 4.0.5 and vitest 5.0.5 - #352
Conversation
Dependency batch. Each bump is the newest version with at least 24 hours of publish age at bump time (2026-10-16T18:17Z): - ai ^7.0.141 -> ^7.0.142 (devDeps: agent, effect, provider; deps: private release-please-ai) - @ai-sdk/provider 4.0.27 -> 4.0.28 (deps: agent, effect, provider; exact pin, required by ai 7.0.142) - @ai-sdk/anthropic ^4.0.80 -> ^4.0.81 (deps: provider, private release-please-ai) - @ai-sdk/openai-compatible ^3.0.69 -> ^3.0.70 (deps: provider) - @ai-sdk/provider-utils ^5.0.60 -> ^5.0.61 (devDeps: effect, sandbox) - @ai-sdk/harness ^1.0.152 -> ^1.0.153 (devDeps: effect, sandbox) - @ai-sdk/harness-claude-code ^1.0.156 -> ^1.0.157 (devDeps: sandbox) - @ai-sdk/react 4.0.145 -> 4.0.146 (devDeps: agent, exact pin) - @ai-sdk/tui ^1.0.142 -> ^1.0.143 (devDeps: sandbox) - @ai-sdk/gateway 4.0.114 -> 4.0.115 (transitive, exact dep of ai) - @ai-sdk/mcp 2.0.76 -> 2.0.77 (transitive, exact dep of react) - effect 4.0.4 -> 4.0.5 (devDeps: effect, exact pin) - vitest ^5.0.4 -> ^5.0.5 and @vitest/coverage-v8 ^5.0.4 -> ^5.0.5 (devDeps; @vitest/mocker and @vitest/spy follow to 5.0.5) Published runtime range changes: @coder/ai-sdk-provider (@ai-sdk/anthropic ^4.0.81, @ai-sdk/openai-compatible ^3.0.70, @ai-sdk/provider 4.0.28), @coder/ai-sdk-agent (@ai-sdk/provider 4.0.28) and @coder/ai-sdk-effect (@ai-sdk/provider 4.0.28). zod stays 4.6.7. No peerDependencies change. Signed-off-by: Thomas Kosiewski <tk@coder.com> --- _Generated with [`xum`](https://github.com/coder/xum) • Model: `anthropic:claude-opus-5-5` • Thinking: `high`_ Change-Id: I58eb7ad67bc013ca5667713382fd0c415ebe8d5f Signed-off-by: Thomas Kosiewski <tk@coder.com>
|
@codex review |
|
@codex security review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Already looking forward to the next diff. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
🛡️ Codex Security ReviewSecurity review completed. No security issues were found in this pull request. Reviewed commit: Only the user who started this review can view the report in Codex. ℹ️ About Codex security reviews in GitHubThis is an experimental Codex feature. Security reviews are triggered when:
Once complete, Codex will leave suggestions, or a comment if no findings are found. |
Daily dependency batch for the AI SDK family, Effect, and Vitest. Every bump is the newest version with at least 24 hours of publish age at bump time (2026-10-16T18:17Z). I re-checked each with
npm view <pkg> time --json. No newer in-line version exists, so nothing is deferred.Versions
ai^7.0.141^7.0.142@ai-sdk/provider4.0.274.0.28(exact)@ai-sdk/anthropic^4.0.80^4.0.81@ai-sdk/openai-compatible^3.0.69^3.0.70@ai-sdk/provider-utils^5.0.60^5.0.61@ai-sdk/harness^1.0.152^1.0.153@ai-sdk/harness-claude-code^1.0.156^1.0.157@ai-sdk/react4.0.1454.0.146(exact)@ai-sdk/tui^1.0.142^1.0.143@ai-sdk/gateway@ai-sdk/mcpeffect4.0.44.0.5(exact)~4.0.0unchangedvitest^5.0.4^5.0.5@vitest/coverage-v8^5.0.4^5.0.5@vitest/mocker,@vitest/spyUnchanged on purpose: zod 4.6.7, tsup
^9.0.0, the TypeScript alias pair, allpeerDependencies, pnpm, Node, mise tools, and Actions.packages/effect/README.mdlists@ai-sdk/provideras "exact (same pin as@coder/ai-sdk-provider)" with no version number, so it needs no edit. It names no@effect/*companion package.Published runtime range changes
dependencieschange@coder/ai-sdk-provider@ai-sdk/anthropic^4.0.80→^4.0.81,@ai-sdk/openai-compatible^3.0.69→^3.0.70,@ai-sdk/provider4.0.27→4.0.28@coder/ai-sdk-agent@ai-sdk/provider4.0.27→4.0.28@coder/ai-sdk-effect@ai-sdk/provider4.0.27→4.0.28(siblings stayworkspace:^)@coder/ai-sdk-sandboxNo
peerDependencieschange in any package.Effect release PR #325
Release PR #325 (
chore(effect): release 0.1.0) is held for the owner's npm steps. This PR does not merge, close, or edit it. Release-please will refresh it after this merge, so it will pin@ai-sdk/provider4.0.28.@coder/ai-sdk-effectdepends on the siblings throughworkspace:^. The provider and agent releases that carry 4.0.28 will reach npm before #325 merges, because #325 stays held until the owner releases it.Lockfile
minimumReleaseAge: 1440and no exclusions, thenpnpm dedupe(already up to date). I restoredpnpm-workspace.yamlbyte for byte, so it is not in the diff.@ai-sdk/provider(4.0.28), onezod(4.6.7), oneeffect(4.0.5).rm -rf node_modules && CI=true pnpm install --frozen-lockfilewith the default store passed (pnpm 11.28.5).pnpm -r outdatedreports nothing after the bump.Tooling freshness
latestdist-tag for pnpm is 12.14.0, a major. It is out of scope here.Validation
Node 26.12.0 and pnpm 11.28.5 from mise.
pnpm exec node --versionprints v26.12.0.pnpm -r build: passpnpm check(oxfmt, oxlint, typecheck): passpnpm -r test: agent 378, sandbox 191, provider 22, release-please-ai 13, effect 96 (unit, live e2e run separately): all passpnpm publint,pnpm attw: passhttps://dogfood.cdr.dev(coder whoamiOK):cd packages/agent && npx vitest run test/e2e: 7/7 (two runs, both 7/7)cd packages/effect && npx vitest run test/e2e: 3/3. A second run throughpnpm exec vitestalso passed 3/3 on Node 26.12.0.npxin this workspace resolves Node 22.19.0 (the engines floor), not the mise Node 26. The agent live runs therefore ran on Node 22.19.0.Generated with
xum• Model:anthropic:claude-opus-5-5• Thinking:high