@ai-sdk/fireworks
3.0.97 · 17 Nov 2026Apache-2.0936k / weekRepositoryHomepagenpmAtom feed
314 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
- 3.x · latest line
3.0.35 – 3.0.4510 releases that only update dependencies@ai-sdk/provider 4.0.10@ai-sdk/provider-utils 5.0.35@ai-sdk/openai-compatible 3.0.42Show each
- 3.0.451 Sep 2026@ai-sdk/provider 4.0.10@ai-sdk/provider-utils 5.0.35@ai-sdk/openai-compatible 3.0.42
- 3.0.4430 Aug 2026@ai-sdk/openai-compatible 3.0.41@ai-sdk/provider 4.0.9@ai-sdk/provider-utils 5.0.34
- 3.0.4328 Aug 2026@ai-sdk/provider-utils 5.0.33@ai-sdk/openai-compatible 3.0.40
- 3.0.4226 Aug 2026@ai-sdk/provider-utils 5.0.32@ai-sdk/openai-compatible 3.0.39
- 3.0.4025 Aug 2026@ai-sdk/provider 4.0.8@ai-sdk/openai-compatible 3.0.37@ai-sdk/provider-utils 5.0.30
- 3.0.3924 Aug 2026@ai-sdk/openai-compatible 3.0.36
- 3.0.3822 Aug 2026@ai-sdk/provider-utils 5.0.29@ai-sdk/openai-compatible 3.0.35
- 3.0.3721 Aug 2026@ai-sdk/openai-compatible 3.0.34
- 3.0.3620 Aug 2026@ai-sdk/openai-compatible 3.0.33
- 3.0.3519 Aug 2026@ai-sdk/provider-utils 5.0.28@ai-sdk/openai-compatible 3.0.32
3.0.34
18 Aug 2026fireworks: Enable structured outputs so response_format json_schema is forwarded instead of degrading to json_object
3.0.23 – 3.0.3311 releases that only update dependencies@ai-sdk/openai-compatible 3.0.31@ai-sdk/provider-utils 5.0.27@ai-sdk/provider 4.0.7Show each
- 3.0.3317 Aug 2026@ai-sdk/openai-compatible 3.0.31
- 3.0.3211 Aug 2026@ai-sdk/provider-utils 5.0.27@ai-sdk/openai-compatible 3.0.30
- 3.0.3110 Aug 2026@ai-sdk/provider-utils 5.0.26@ai-sdk/openai-compatible 3.0.29
- 3.0.309 Aug 2026@ai-sdk/openai-compatible 3.0.28
- 3.0.297 Aug 2026@ai-sdk/provider 4.0.7@ai-sdk/provider-utils 5.0.25@ai-sdk/openai-compatible 3.0.27
- 3.0.287 Aug 2026@ai-sdk/provider-utils 5.0.24@ai-sdk/openai-compatible 3.0.26
- 3.0.276 Aug 2026@ai-sdk/provider 4.0.6@ai-sdk/openai-compatible 3.0.25@ai-sdk/provider-utils 5.0.23
- 3.0.266 Aug 2026@ai-sdk/provider-utils 5.0.22@ai-sdk/openai-compatible 3.0.24
- 3.0.254 Aug 2026@ai-sdk/provider-utils 5.0.21@ai-sdk/openai-compatible 3.0.23
- 3.0.244 Aug 2026@ai-sdk/provider-utils 5.0.20@ai-sdk/openai-compatible 3.0.22
- 3.0.233 Aug 2026@ai-sdk/provider 4.0.5@ai-sdk/openai-compatible 3.0.21@ai-sdk/provider-utils 5.0.19
3.0.22
1 Aug 2026Parse the object error envelope Fireworks actually returns (
{"error":{"object","type","code","message"}}) instead of a bare string. The mismatched schema failed to parse, so error messages silently degraded to the HTTP reason phrase —Bad Requestover HTTP/1.1, and an empty string over HTTP/2, which has no reason phrase. Fireworks' own message now reaches the caller, e.g.Model not found, inaccessible, and/or not deployedrather thanNot Found.
3.0.11 – 3.0.2111 releases that only update dependencies@ai-sdk/provider-utils 5.0.18@ai-sdk/openai-compatible 3.0.20@ai-sdk/provider 4.0.4Show each
- 3.0.2131 Jul 2026@ai-sdk/provider-utils 5.0.18@ai-sdk/openai-compatible 3.0.20
- 3.0.2031 Jul 2026@ai-sdk/provider-utils 5.0.17@ai-sdk/openai-compatible 3.0.19
- 3.0.1930 Jul 2026@ai-sdk/provider-utils 5.0.16@ai-sdk/openai-compatible 3.0.18
- 3.0.1829 Jul 2026@ai-sdk/provider-utils 5.0.15@ai-sdk/openai-compatible 3.0.17
- 3.0.1728 Jul 2026@ai-sdk/provider-utils 5.0.14@ai-sdk/openai-compatible 3.0.16
- 3.0.1627 Jul 2026@ai-sdk/provider 4.0.4@ai-sdk/openai-compatible 3.0.15@ai-sdk/provider-utils 5.0.13
- 3.0.1521 Jul 2026@ai-sdk/provider-utils 5.0.12@ai-sdk/openai-compatible 3.0.14
- 3.0.1420 Jul 2026@ai-sdk/openai-compatible 3.0.13
- 3.0.1317 Jul 2026@ai-sdk/provider-utils 5.0.11@ai-sdk/openai-compatible 3.0.12
- 3.0.1215 Jul 2026@ai-sdk/openai-compatible 3.0.11
- 3.0.1114 Jul 2026@ai-sdk/provider-utils 5.0.10@ai-sdk/openai-compatible 3.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.8
9 Jul 2026fireworks: Add
providerOptionsschema and type for Fireworks image model requests
Patch Changes
fireworks: Add
providerOptionsschema and type for Fireworks image model requests
3.0.7
8 Jul 2026Only updates dependencies:@ai-sdk/provider-utils 5.0.6@ai-sdk/openai-compatible 3.0.6
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.3 – 3.0.53 releases that only update dependencies@ai-sdk/provider-utils 5.0.4@ai-sdk/openai-compatible 3.0.4@ai-sdk/provider 4.0.1Show each
3.0.2
27 Jun 2026Add
serviceTierprovider option for Fireworks chat models.
3.0.1
27 Jun 2026Only updates dependencies:@ai-sdk/provider-utils 5.0.1@ai-sdk/openai-compatible 3.0.1
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
Raise minimum supported Node.js version to 22. Supported versions: 22, 24, and 26.
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
Patch Changes
Add AI Gateway hint to provider READMEs
Migrate providers to support new top-level
reasoningparameterEnable
includeUsagefor Fireworks so streaming responses report token usageAdd the
promptCacheKeyprovider option for Fireworks prompt cache affinity
and Kimi K2.6 model autocomplete, and remove the deprecated Kimi K2.5
serverless model from autocomplete.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.99 – 2.0.1046 releases that only update dependencies@ai-sdk/provider-utils 4.0.67@ai-sdk/openai-compatible 2.0.94Show each
- 2.0.10417 Nov 2026@ai-sdk/provider-utils 4.0.67@ai-sdk/openai-compatible 2.0.94
- 2.0.10310 Nov 2026@ai-sdk/provider-utils 4.0.66@ai-sdk/openai-compatible 2.0.93
- 2.0.1027 Nov 2026@ai-sdk/provider-utils 4.0.65@ai-sdk/openai-compatible 2.0.92
- 2.0.1016 Nov 2026@ai-sdk/openai-compatible 2.0.91
- 2.0.1003 Nov 2026@ai-sdk/openai-compatible 2.0.90@ai-sdk/provider-utils 4.0.64
- 2.0.992 Nov 2026@ai-sdk/openai-compatible 2.0.89
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.