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

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
ai (source)	7.0.48 → 7.0.58

---

Release Notes

vercel/ai (ai)

v7.0.58

Compare Source

Patch Changes

• 72ad23f: Respect ToolLoopAgent timeouts configured in agent settings.

• ad6a650: feat(video): allow aspectRatio: 'adaptive' on generateVideo

  Some video models derive the output ratio from the input and reject explicit
  {width}:{height} values — BytePlus Seedance 2.5 does this for first-frame,
  first-and-last-frame, editing, and extension tasks. aspectRatio on
  VideoModelV3CallOptions, VideoModelV4CallOptions, and
  experimental_generateVideo is now `${number}:${number}` | 'adaptive', so
  those calls no longer need a type assertion. Support is provider-specific.

• 81cd026: Reduce bundle size by making internal Zod v4 imports tree-shakeable.

• Updated dependencies [c477556]

• Updated dependencies [ad6a650]

• Updated dependencies [81cd026]

  • @​ai-sdk/gateway@​4.0.46
  • @​ai-sdk/provider@​4.0.7
  • @​ai-sdk/provider-utils@​5.0.25

v7.0.57

Compare Source

Patch Changes

• Updated dependencies [1937bef]
  • @​ai-sdk/provider-utils@​5.0.24
  • @​ai-sdk/gateway@​4.0.45

v7.0.56

Compare Source

Patch Changes

• 25c9120: Expose provider metadata on language-model-call end callbacks and telemetry spans.

• 89080c8: fix (ai/gateway): make retried doStart calls idempotent

  generateVideo retries doStart, which creates a billable generation, so a
  retry after a lost response could start a second one. It now mints one
  idempotency token per logical start — outside the retry closure — and forwards it
  as an idempotency-key header, so a provider that deduplicates (the Vercel AI
  Gateway does) sees the same key on every attempt. GatewayVideoModel simply
  forwards the caller's headers rather than inferring retry identity from an
  options object, which would collide across unrelated calls.

• 79d6195: Stop pending and active resumed chat streams after cancellation, and prevent
  overlapping resumptions from applying stale updates.

• Updated dependencies [89080c8]

• Updated dependencies [89080c8]

  • @​ai-sdk/gateway@​4.0.44

v7.0.55

Compare Source

Patch Changes

• 3469d0c: feat: add batch APIs
• Updated dependencies [3469d0c]
  • @​ai-sdk/provider@​4.0.6
  • @​ai-sdk/gateway@​4.0.43
  • @​ai-sdk/provider-utils@​5.0.23

v7.0.54

Compare Source

Patch Changes

• a6b17a2: Allow ToolLoopAgent prepareCall callbacks to read and override the top-level reasoning option.
• 5615eb7: Add defaultInstructionsMiddleware for applying default language model instructions while preserving call-level overrides.
• 36a3ff6: Preserve preceding assistant messages when regenerating a response.

v7.0.52

Compare Source

Patch Changes

• 3836a85: Skip re-validating tool input for terminal output-available UI message parts.
• Updated dependencies [1bec07d]
• Updated dependencies [53c326e]
• Updated dependencies [d765f82]
  • @​ai-sdk/provider-utils@​5.0.21
  • @​ai-sdk/gateway@​4.0.41

v7.0.51

Compare Source

Patch Changes

• Updated dependencies [160ccdb]
  • @​ai-sdk/provider-utils@​5.0.20
  • @​ai-sdk/gateway@​4.0.40

v7.0.50

Compare Source

Patch Changes

• 79e133c: async APIs for generateVideo (poll, webhook)

  Adds an asynchronous start/status flow to the experimental video model
  interface (VideoModelV4): models may now implement doStart, doStatus,
  and handleWebhookOption instead of (or in addition to) doGenerate, and
  experimental_generateVideo accepts poll and webhook options to
  orchestrate completion via polling or webhooks. Polling configuration can use
  a custom delay implementation for durable workflow compatibility.

• da64b51: feat(code-mode): simplify tool caller configuration

• Updated dependencies [79e133c]

  • @​ai-sdk/provider@​4.0.5
  • @​ai-sdk/gateway@​4.0.39
  • @​ai-sdk/provider-utils@​5.0.19

v7.0.49

Compare Source

Patch Changes

• Updated dependencies [fb6d2f8]
  • @​ai-sdk/gateway@​4.0.38

---

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.