Packages

@ai-sdk/fireworks

3.0.97 · 17 Nov 2026Apache-2.0936k / weekRepositoryHomepagenpmAtom feed

Your version

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

  1. 1.0.63 – 1.0.664 releases that only update dependencies@ai-sdk/provider-utils 3.0.45@ai-sdk/openai-compatible 1.0.62Show each
  2. 1.0.62

    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.

  3. 1.0.52 – 1.0.618 releases that only update dependencies@ai-sdk/provider-utils 3.0.40@ai-sdk/openai-compatible 1.0.57@ai-sdk/provider 2.0.5Show each
  4. 1.0.51

    2 Aug 2026
    • Parse 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 Request over 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 deployed rather than Not Found.

  5. 1.0.50

    1 Aug 2026
    • Send promptCacheKey, serviceTier, reasoningHistory and thinking.budgetTokens under the snake_case names the Fireworks API defines. Fireworks rejects unknown fields outright, so previously any of these provider options failed the whole request with 400 Extra inputs are not permitted.

  6. 1.0.43 – 1.0.497 releases that only update dependencies@ai-sdk/provider-utils 3.0.31@ai-sdk/openai-compatible 1.0.47Show each
  7. 1.0.42

    12 Jun 2026
    • Enable includeUsage for Fireworks so streaming responses report token usage

  8. 1.0.41

    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.

  9. 1.0.39 – 1.0.402 releases that only update dependencies@ai-sdk/openai-compatible 1.0.39@ai-sdk/provider-utils 3.0.25@ai-sdk/provider 2.0.3Show each
  10. 1.0.38

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

  11. 1.0.37

    17 Apr 2026
    • Add AI Gateway hint to provider READMEs

  12. 1.0.32 – 1.0.365 releases that only update dependencies@ai-sdk/provider-utils 3.0.23@ai-sdk/openai-compatible 1.0.35Show each
  13. 1.0.31

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

  14. 1.0.28 – 1.0.303 releases that only update dependencies@ai-sdk/provider-utils 3.0.19@ai-sdk/openai-compatible 1.0.29Show each
  15. 1.0.27

    3 Nov 2025
    • backport: Test server

  16. 1.0.20 – 1.0.267 releases that only update dependencies@ai-sdk/provider-utils 3.0.15@ai-sdk/openai-compatible 1.0.25Show each
  17. 1.0.19

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

  18. 1.0.14 – 1.0.184 releases that only update dependencies@ai-sdk/openai-compatible 1.0.18@ai-sdk/provider-utils 3.0.8Show 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.