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. 2.x
  2. 2.0.3 – 2.0.53 releases that only update dependencies@ai-sdk/provider-utils 4.0.5@ai-sdk/provider 3.0.2Show each
  3. 2.0.2

    30 Dec 2025
    • Trigger release to update @latest

  4. 2.0.1

    23 Dec 2025

    Only updates a dependency:@ai-sdk/provider-utils 4.0.1

  5. 2.0.0

    22 Dec 2025
    • Breaking

      Ai SDK 6 beta

    • provider: Add specificationVersion to ProviderV3

    • replicate: Add configurable maxWaitTimeInSeconds option for image generation

      Added maxWaitTimeInSeconds provider option to control sync wait duration for Replicate image predictions:

      This allows longer predictions to complete by extending the sync timeout beyond the default 60 seconds.

  6. 1.x
  7. 1.0.45 – 1.0.484 releases that only update dependencies@ai-sdk/provider-utils 3.0.46Show each
  8. 1.0.44

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

  9. 1.0.43

    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.

  10. 1.0.29 – 1.0.4213 releases that only update dependencies@ai-sdk/provider-utils 3.0.40@ai-sdk/provider 2.0.5Show each
  11. 1.0.28

    12 Jun 2026
    • Only send provider credentials to same-origin response-supplied URLs

      Several provider clients followed a URL taken from the provider's API response (a polling/status URL or a final media URL such as polling_url, urls.get, result_url, result.sample, or video.uri) and reused the authenticated headers — or appended ?key=<API_KEY> — on that request. Because the host of the response-supplied URL was never validated, the long-lived API key was sent to whatever host the response named (a CDN in the benign case, or an attacker-chosen host if the provider response was tampered with), allowing credential exfiltration.

      A new isSameOrigin helper is added to @ai-sdk/provider-utils, and the affected fetches in @ai-sdk/black-forest-labs, @ai-sdk/fireworks, @ai-sdk/replicate, @ai-sdk/gladia, @ai-sdk/fal, and @ai-sdk/google now attach credentials only when the followed URL is same-origin with the provider's configured API origin. Requests to a foreign origin are made without the credential.

  12. 1.0.26

    29 Apr 2026
    • Trigger release for all packages after provenance setup

  13. 1.0.25

    17 Apr 2026
    • Add AI Gateway hint to provider READMEs

  14. 1.0.22 – 1.0.243 releases that only update dependencies@ai-sdk/provider-utils 3.0.23Show each
  15. 1.0.21

    30 Dec 2025
    • Trigger new release for @ai-v5 dist-tag

  16. 1.0.18 – 1.0.203 releases that only update dependencies@ai-sdk/provider-utils 3.0.19Show each
  17. 1.0.17

    3 Nov 2025
    • backport: Test server

  18. 1.0.11 – 1.0.166 releases that only update dependencies@ai-sdk/provider-utils 3.0.15Show each
  19. 1.0.10

    23 Sep 2025
    • Add provider version to user-agent header

  20. 1.0.4 – 1.0.96 releases that only update dependencies@ai-sdk/provider-utils 3.0.9Show 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.