Packages

@ai-sdk/replicate

3.0.85 · 17 Nov 2026Apache-2.0111.4k / weekRepositoryHomepagenpmAtom feed

Your version

234 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.

  1. 3.x · latest line
  2. 3.0.21 – 3.0.3312 releases that only update dependencies@ai-sdk/provider-utils 5.0.32@ai-sdk/provider 4.0.8Show each
  3. 3.0.20

    3 Aug 2026
    • 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.

  4. 3.0.11 – 3.0.199 releases that only update dependencies@ai-sdk/provider-utils 5.0.18@ai-sdk/provider 4.0.4Show each
  5. 3.0.10

    13 Jul 2026
    • provider-utils: Validate provider-response URLs in getFromApi

      getFromApi now has a validateUrl flag. It is optional so existing callers keep compiling (omitting it behaves like false, i.e. no validation), but all AI SDK provider packages set it explicitly at every call site so each one makes a visible trust decision. When true, the URL is routed through fetchWithValidatedRedirects — the same guard used by downloadBlob — which rejects private/loopback/link-local targets, re-validates every redirect hop, strips proxy/metadata/cookie request headers, and drops all caller headers except the user-agent on cross-origin redirects (custom API-key headers must not follow a redirect off-origin any more than Authorization may); blocked URLs throw DownloadError. It is enabled at the image/video/audio download and polling call sites where the URL comes from a provider response body; URLs built from developer-configured endpoints pass validateUrl: false and are unaffected.

      A new optional credentialedOrigin withholds caller headers unless the URL is same-origin with it, so the API key is not sent to a response-supplied host on a different origin.

      A new optional trustedOrigin exempts URLs (and redirect hops) that are same-origin with the developer-configured provider endpoint from target validation, so self-hosted and localhost deployments whose response URLs point back at the configured host keep working; all other hops are still validated.

      Also closes range gaps in validateDownloadUrl (IPv4 224.0.0.0/4 multicast and the TEST-NET documentation ranges 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24; IPv6 documentation ranges 2001:db8::/32 and 3fff::/20), and follows only the fetch-spec redirect status codes (301/302/303/307/308) — a Location header on any other status is not followed. This guard performs string/literal checks only and does not resolve DNS; hostnames that resolve to private addresses and DNS rebinding remain out of scope and must be constrained at the network layer (or by injecting a Node fetch that pins the resolved IP at connect time) for server deployments handling untrusted URLs. See contributing/secure-url-handling.md.

    • Reject empty OpenAI, Anthropic, and Replicate base URLs with a helpful AI SDK
      invalid argument error.

  6. 3.0.7 – 3.0.82 releases that only update dependencies@ai-sdk/provider 4.0.3@ai-sdk/provider-utils 5.0.7Show each
  7. 3.0.6

    2 Jul 2026
    • Add experimental streaming transcription support for transcription models, including OpenAI gpt-realtime-whisper and xAI WebSocket STT.

  8. 3.0.1 – 3.0.55 releases with no change for you4 dependency updates, 1 maintenance@ai-sdk/provider-utils 5.0.4@ai-sdk/provider 4.0.1Show each
  9. 3.0.0

    25 Jun 2026
    • Breaking

      Remove CommonJS exports from all packages. All packages are now ESM-only ("type": "module"). Consumers using require() must switch to ESM import syntax.

    • Breaking

      Start v7 pre-release

    • Breaking

      Make provider implementations code patterns more consistent, including renaming certain exported symbols

      For all externally exported symbols that were renamed, the old names continue to work via deprecated aliases.

  10. 2.x
  11. 2.0.69 – 2.0.735 releases that only update dependencies@ai-sdk/provider-utils 4.0.67Show each
  12. 2.0.68

    21 Oct 2026
    • Defer validation schema construction until first use to reduce provider import time.

  13. 2.0.64 – 2.0.674 releases that only update dependencies@ai-sdk/provider-utils 4.0.61@ai-sdk/provider 3.0.19Show each
  14. 2.0.63

    30 Sep 2026
    • Keep default Node.js downloads protected by DNS validation and connection pinning when frameworks or instrumentation wrap global fetch before or after the SDK loads.

  15. 2.0.56 – 2.0.627 releases that only update dependencies@ai-sdk/provider-utils 4.0.56@ai-sdk/provider 3.0.18Show each

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.