chore(deps): update dependency ai to v7.0.66

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
ai (source)	7.0.58 → 7.0.66

---

Release Notes

vercel/ai (ai)

v7.0.66

Compare Source

Patch Changes

• 0782259: Keep chat status submitted until response content begins streaming.
• 2fd1214: Fix declaration emit for exported values that infer an Output type.

v7.0.65

Compare Source

Patch Changes

• dc8caae: Avoid repeatedly cloning accumulated text in readUIMessageStream while
  preserving independent snapshots for mutable nested values.
• 72ec74f: Preserve root-level JSON Schema definitions when wrapping array output schemas.
• c5b0515: Propagate errors thrown by the Chat onFinish callback to the initiating request.
• Updated dependencies [16650e9]
  • @​ai-sdk/gateway@​4.0.52

v7.0.64

Compare Source

Patch Changes

• Updated dependencies [ea75787]
• Updated dependencies [b20de9e]
  • @​ai-sdk/gateway@​4.0.51

v7.0.63

Compare Source

Patch Changes

• d0a5807: Preserve reasoning block IDs from UI message streams on reasoning UI parts.
• dcf33e8: Allow providers without reranking model support to be assigned to Provider.
• Updated dependencies [a4d386d]
  • @​ai-sdk/gateway@​4.0.50

v7.0.62

Patch Changes

• e0bcf52: feat(ui): add typed custom bodies to Completion APIs

v7.0.61

Patch Changes

• 326054b: Prevent resumeStream from copying the previous assistant message into the resumed response.
• 975bb28: Cancel messages that are still being prepared when a chat is stopped.
• Updated dependencies [7fbfc6d]
  • @​ai-sdk/provider-utils@​5.0.27
  • @​ai-sdk/gateway@​4.0.49

v7.0.60

Patch Changes

• 79c52ef: Align ToolLoopAgent prepareCall types with the settings available and honored at runtime.
• Updated dependencies [3cc1bb6]
  • @​ai-sdk/gateway@​4.0.48

v7.0.59

Compare Source

Patch Changes

• Updated dependencies [401a4ba]
• Updated dependencies [7af9646]
  • @​ai-sdk/provider-utils@​5.0.26
  • @​ai-sdk/gateway@​4.0.47

---

Configuration

📅 Schedule: (in timezone Europe/Rome)

• Branch creation
  • Between 12:00 AM and 06:59 AM, only on Sunday and Saturday (* 0-6 * * 6,0)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

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

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

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: demos/weather-assistant/pnpm-lock.yaml

? Verifying lockfile against supply-chain policies (325 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 9, reused 0, downloaded 0, added 0
Progress: resolved 48, reused 0, downloaded 1, added 0
Progress: resolved 266, reused 0, downloaded 1, added 0
✗ Lockfile failed supply-chain policy check (325 entries in 3.5s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification:
  @ai-sdk/anthropic@2.0.94 was published at 2026-08-07T02:55:57.000Z, within the minimumReleaseAge cutoff (2026-08-07T02:38:37.185Z)

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.

File name: demos/real-estate-agent/pnpm-lock.yaml

? Verifying lockfile against supply-chain policies (310 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 6, reused 0, downloaded 1, added 0
✗ Lockfile failed supply-chain policy check (310 entries in 2s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification:
  @ai-sdk/anthropic@2.0.94 was published at 2026-08-07T03:03:07.752Z, within the minimumReleaseAge cutoff (2026-08-07T02:38:44.619Z)

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.