@ai-sdk/open-responses@2.0.0
Major Changes
-
ef992f8: Remove CommonJS exports from all packages. All packages are now ESM-only (
"type": "module"). Consumers usingrequire()must switch to ESMimportsyntax. -
c29a26f: feat(provider): add support for provider references and uploading files as supported per provider
-
8359612: Start v7 pre-release
-
04e9009: chore: 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
-
74d520f: feat: migrate providers to support new top-level
reasoningparameter -
9f0e36c: trigger release for all packages after provenance setup
-
58a2ad7: fix: more precise default message for tool execution denial
-
fb82a6c: Harden streamed tool call argument handling against prototype pollution.
-
7fc6bd6: Raise minimum supported Node.js version to 22. Supported versions: 22, 24, and 26.
-
0c4c275: trigger initial canary release
-
8831e80: chore(provider/open-responses): update provider to use v4 types
-
9bd6512: feat(provider): change file part data property to be tagged with a type and remove the image part type
-
258c093: chore: ensure consistent import handling and avoid import duplicates or cycles
-
e69a836: feat(open-responses): add option to pass reasoning summary for OpenResponses
-
5463d0d: feat(provider): align tool result output content file part types with top-level message file part types
-
b8396f0: trigger initial beta release
-
90e2d8a: chore: fix unused vars not being flagged by our lint tooling
-
52d2e30: fix(open-responses): map non-image file parts to input_file
-
b3976a2: 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. -
ff5eba1: feat: roll
image-*tool output types into their equivalentfile-*types