[mchesterbot]

This PR contains the following updates:

Package	Type	Update	Change
ai (source)	dependencies	patch	7.0.155 → 7.0.159

---

Release Notes

vercel/ai (ai)

v7.0.159

Compare Source

Patch Changes

• Updated dependencies [cbc9ac0]
  • @​ai-sdk/gateway@4.0.132

v7.0.158

Compare Source

Patch Changes

• 8ba3a5c: fix(ai): repair partial JSON that ends with a minus sign at the start of an array

• 5c247e9: feat(sandbox): add stat, listDirectory, and deleteFile to Experimental_SandboxSession, and specify that relative paths in every method resolve against the directory run and spawn start in

  The just-bash and Vercel Sandbox adapters implement the new methods. Both now resolve a relative workingDirectory for run and spawn against the sandbox's working directory, and the just-bash adapter rejects writes to a directory instead of replacing it with a file.

• Updated dependencies [7716e18]

• Updated dependencies [f850782]

• Updated dependencies [5c247e9]

• Updated dependencies [dcd2f8d]

  • @​ai-sdk/gateway@4.0.131
  • @​ai-sdk/provider-utils@5.0.72
  • @​ai-sdk/provider@4.0.35

v7.0.157

Compare Source

Patch Changes

• 0cc4921: graduate LanguageModelStreamPart to stable and deprecate Experimental_LanguageModelStreamPart
• 077cfb3: feat(ai): Graduate filterActiveTools from experimental. It is now exported as filterActiveTools; experimental_filterActiveTools remains as a deprecated alias.
• eb768e2: Fix Next.js Edge Runtime warnings from Node.js runtime detection used by telemetry tracing.
• Updated dependencies [9ca8bcf]
• Updated dependencies [61a315e]
  • @​ai-sdk/gateway@4.0.130
  • @​ai-sdk/provider-utils@5.0.71

v7.0.156

Compare Source

Patch Changes

• Updated dependencies [9f19c79]
  • @​ai-sdk/gateway@4.0.129

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[claude]

Claude finished @mchesterbot[bot]'s task in 19s —— View job

---

Review of PR #479 (ai 7.0.155 → 7.0.159)

I read the diff only. I did not run lint, typecheck or tests.

Scope: package.json and package-lock.json change, and nothing else. The ai pin is exact, as the repo expects.

Findings

• Title and description are out of date. The branch now pins ai at 7.0.159, but the title and body still say 7.0.158. The commit on the branch is "Update dependency ai to v7.0.159". The code is fine, and Renovate should refresh the text on its next run.
• Duplicate @ai-sdk/provider copies. ai and @ai-sdk/gateway now need @ai-sdk/provider 4.0.35 and @ai-sdk/provider-utils 5.0.72. The root @ai-sdk/provider stays at 4.0.34 because @ai-sdk/anthropic, google, openai and openai-compatible (exact pins in package.json) still use it. The lockfile therefore nests a second @ai-sdk/provider 4.0.35 under both ai and @ai-sdk/gateway.
  • This looks harmless, because @ai-sdk/provider is mostly types and small helpers. The risk is a type mismatch, since two copies of the provider types can make LanguageModel values from the provider packages differ from the ones ai expects. npm run typecheck in CI will show whether that happens.
  • It should go away once Renovate bumps the provider packages. I would merge those bumps together with this one if CI complains.
• Behaviour changes in 7.0.156–7.0.159. These are patch-level notes only:
  • Partial-JSON repair now handles a trailing - at the start of an array. This affects streamed structured output and is only a fix.
  • filterActiveTools is graduated, and the Experimental sandbox and stream-part types have changed. A grep of the repo found no use of experimental_filterActiveTools, Experimental_LanguageModelStreamPart or Experimental_Sandbox*, so none of it affects this codebase.
  • The Edge-runtime warning fix is harmless.
• Security and performance: no concerns. The new lockfile entries use registry URLs with integrity hashes, and the nested package adds only the json-schema dependency.
• Test coverage: no new tests are needed for a dependency bump. Merge once Typecheck, Unit Tests and Build pass. The LLM paths (lib/llm/*) are the ones to watch.

Verdict: looks fine to merge once CI is green.