@ai-sdk/fal
3.0.85 · 17 Nov 2026Apache-2.093.1k / weekRepositoryHomepagenpmAtom feed
234 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
- 3.x · latest line
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.0.3326 Aug 2026@ai-sdk/provider-utils 5.0.32
- 3.0.3125 Aug 2026@ai-sdk/provider 4.0.8@ai-sdk/provider-utils 5.0.30
- 3.0.3022 Aug 2026@ai-sdk/provider-utils 5.0.29
- 3.0.2919 Aug 2026@ai-sdk/provider-utils 5.0.28
- 3.0.2811 Aug 2026@ai-sdk/provider-utils 5.0.27
- 3.0.2710 Aug 2026@ai-sdk/provider-utils 5.0.26
- 3.0.267 Aug 2026@ai-sdk/provider 4.0.7@ai-sdk/provider-utils 5.0.25
- 3.0.257 Aug 2026@ai-sdk/provider-utils 5.0.24
- 3.0.246 Aug 2026@ai-sdk/provider 4.0.6@ai-sdk/provider-utils 5.0.23
- 3.0.236 Aug 2026@ai-sdk/provider-utils 5.0.22
- 3.0.224 Aug 2026@ai-sdk/provider-utils 5.0.21
- 3.0.214 Aug 2026@ai-sdk/provider-utils 5.0.20
3.0.20
3 Aug 2026Async APIs for generateVideo (poll, webhook)
Adds an asynchronous start/status flow to the experimental video model
interface (VideoModelV4): models may now implementdoStart,doStatus,
andhandleWebhookOptioninstead of (or in addition to)doGenerate, andexperimental_generateVideoacceptspollandwebhookoptions to
orchestrate completion via polling or webhooks. Polling configuration can use
a custom delay implementation for durable workflow compatibility.
Patch Changes
Async APIs for generateVideo (poll, webhook)
Adds an asynchronous start/status flow to the experimental video model
interface (VideoModelV4): models may now implementdoStart,doStatus,
andhandleWebhookOptioninstead of (or in addition to)doGenerate, andexperimental_generateVideoacceptspollandwebhookoptions to
orchestrate completion via polling or webhooks. Polling configuration can use
a custom delay implementation for durable workflow compatibility.
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
- 3.0.1931 Jul 2026@ai-sdk/provider-utils 5.0.18
- 3.0.1831 Jul 2026@ai-sdk/provider-utils 5.0.17
- 3.0.1730 Jul 2026@ai-sdk/provider-utils 5.0.16
- 3.0.1629 Jul 2026@ai-sdk/provider-utils 5.0.15
- 3.0.1528 Jul 2026@ai-sdk/provider-utils 5.0.14
- 3.0.1427 Jul 2026@ai-sdk/provider 4.0.4@ai-sdk/provider-utils 5.0.13
- 3.0.1321 Jul 2026@ai-sdk/provider-utils 5.0.12
- 3.0.1217 Jul 2026@ai-sdk/provider-utils 5.0.11
- 3.0.1114 Jul 2026@ai-sdk/provider-utils 5.0.10
3.0.10
13 Jul 2026provider-utils: Validate provider-response URLs in
getFromApigetFromApinow has avalidateUrlflag. It is optional so existing callers keep compiling (omitting it behaves likefalse, 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. Whentrue, the URL is routed throughfetchWithValidatedRedirects— the same guard used bydownloadBlob— 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 thanAuthorizationmay); blocked URLs throwDownloadError. 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 passvalidateUrl: falseand are unaffected.A new optional
credentialedOriginwithholds 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
trustedOriginexempts 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(IPv4224.0.0.0/4multicast and the TEST-NET documentation ranges192.0.2.0/24,198.51.100.0/24,203.0.113.0/24; IPv6 documentation ranges2001:db8::/32and3fff::/20), and follows only the fetch-spec redirect status codes (301/302/303/307/308) — aLocationheader 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 Nodefetchthat pins the resolved IP at connect time) for server deployments handling untrusted URLs. Seecontributing/secure-url-handling.md.
Patch Changes
provider-utils: Validate provider-response URLs in
getFromApigetFromApinow has avalidateUrlflag. It is optional so existing callers keep compiling (omitting it behaves likefalse, 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. Whentrue, the URL is routed throughfetchWithValidatedRedirects— the same guard used bydownloadBlob— 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 thanAuthorizationmay); blocked URLs throwDownloadError. 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 passvalidateUrl: falseand are unaffected.A new optional
credentialedOriginwithholds 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
trustedOriginexempts 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(IPv4224.0.0.0/4multicast and the TEST-NET documentation ranges192.0.2.0/24,198.51.100.0/24,203.0.113.0/24; IPv6 documentation ranges2001:db8::/32and3fff::/20), and follows only the fetch-spec redirect status codes (301/302/303/307/308) — aLocationheader 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 Nodefetchthat pins the resolved IP at connect time) for server deployments handling untrusted URLs. Seecontributing/secure-url-handling.md.
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
3.0.6
2 Jul 2026Add experimental streaming transcription support for transcription models, including OpenAI
gpt-realtime-whisperand xAI WebSocket STT.
Patch Changes
Add experimental streaming transcription support for transcription models, including OpenAI
gpt-realtime-whisperand xAI WebSocket STT.
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
- 3.0.52 Jul 2026@ai-sdk/provider-utils 5.0.4
- 3.0.41 Jul 2026@ai-sdk/provider-utils 5.0.3
- 3.0.330 Jun 2026@ai-sdk/provider 4.0.1@ai-sdk/provider-utils 5.0.2
- 3.0.227 Jun 2026@ai-sdk/provider-utils 5.0.1
- 3.0.127 Jun 2026docs, tests or tooling
3.0.0
25 Jun 2026- Breaking
Remove CommonJS exports from all packages. All packages are now ESM-only (
"type": "module"). Consumers usingrequire()must switch to ESMimportsyntax. - 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.
Major Changes
- Breaking
Remove CommonJS exports from all packages. All packages are now ESM-only (
"type": "module"). Consumers usingrequire()must switch to ESMimportsyntax. - 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.
Patch Changes
Add AI Gateway hint to provider READMEs
Trigger release for all packages after provenance setup
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, orvideo.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
isSameOriginhelper 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/googlenow 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.- Breaking
Raise minimum supported Node.js version to 22. Supported versions: 22, 24, and 26.
Trigger initial canary release
Trigger initial beta release
Add workflow serialization support to all provider models.
@ai-sdk/provider-utils: NewserializeModel()helper that extracts only serializable properties from a model instance, filtering out functions and objects containing functions. Third-party provider authors can use this to add workflow support to their own models.All providers:
headersis now optional in provider config types. This is non-breaking — existing code that passesheaderscontinues to work. Custom provider implementations that construct model configs manually can now omitheaders, which is useful when models are deserialized from a workflow step boundary where auth is provided separately.All provider model classes now include
WORKFLOW_SERIALIZEandWORKFLOW_DESERIALIZEstatic methods, enabling them to cross workflow step boundaries without serialization errors.
- 2.x
2.0.70 – 2.0.745 releases that only update dependencies@ai-sdk/provider-utils 4.0.67Show each
- 2.0.7417 Nov 2026@ai-sdk/provider-utils 4.0.67
- 2.0.7310 Nov 2026@ai-sdk/provider-utils 4.0.66
- 2.0.727 Nov 2026@ai-sdk/provider-utils 4.0.65
- 2.0.713 Nov 2026@ai-sdk/provider-utils 4.0.64
- 2.0.7029 Oct 2026@ai-sdk/provider-utils 4.0.63
2.0.69
21 Oct 2026Defer validation schema construction until first use to reduce provider import time.
Encode provider-returned identifiers in follow-up request paths with a shared encodePathSegment helper.
Patch Changes
Defer validation schema construction until first use to reduce provider import time.
Encode provider-returned identifiers in follow-up request paths with a shared encodePathSegment helper.
2.0.65 – 2.0.684 releases that only update dependencies@ai-sdk/provider-utils 4.0.61@ai-sdk/provider 3.0.19Show each
- 2.0.6816 Oct 2026@ai-sdk/provider-utils 4.0.61
- 2.0.6715 Oct 2026@ai-sdk/provider 3.0.19@ai-sdk/provider-utils 4.0.60
- 2.0.6615 Oct 2026@ai-sdk/provider-utils 4.0.59
- 2.0.6513 Oct 2026@ai-sdk/provider-utils 4.0.58
2.0.64
30 Sep 2026Keep default Node.js downloads protected by DNS validation and connection pinning when frameworks or instrumentation wrap global fetch before or after the SDK loads.
Patch Changes
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.
2.0.57 – 2.0.637 releases that only update dependencies@ai-sdk/provider-utils 4.0.56@ai-sdk/provider 3.0.18Show each
- 2.0.6328 Sep 2026@ai-sdk/provider-utils 4.0.56
- 2.0.6227 Sep 2026@ai-sdk/provider 3.0.18@ai-sdk/provider-utils 4.0.55
- 2.0.6123 Sep 2026@ai-sdk/provider-utils 4.0.54
- 2.0.6023 Sep 2026@ai-sdk/provider 3.0.17@ai-sdk/provider-utils 4.0.53
- 2.0.5921 Sep 2026@ai-sdk/provider-utils 4.0.52
- 2.0.589 Sep 2026@ai-sdk/provider 3.0.16@ai-sdk/provider-utils 4.0.51
- 2.0.5730 Aug 2026@ai-sdk/provider-utils 4.0.50
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.