Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: openai/openai-node
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v5.23.2
Choose a base ref
...
head repository: openai/openai-node
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v6.0.0
Choose a head ref
  • 3 commits
  • 56 files changed
  • 4 contributors

Commits on Sep 30, 2025

  1. chore: compat with zod v4 (#1658)

    Co-authored-by: Hernawan Faiz Abdillah <hernawan.faiz.abdillah@gmail.com>
    Co-authored-by: Robert Craigie <robert@craigie.dev>
    3 people authored and stainless-app[bot] committed Sep 30, 2025
    Configuration menu
    Copy the full SHA
    24ff31a View commit details
    Browse the repository at this point in the history
  2. feat(api): Support images and files for function call outputs in resp…

    …onses, BatchUsage
    
    This release introduces a major version change to reflect a breaking modification in the `ResponseFunctionToolCallOutputItem` and `ResponseCustomToolCallOutput` schemas. Specifically, the `output` field, which previously accepted only a `string` value, has been expanded to support multiple structured types:
    
    ```
    Before:  output: string
    After:   output: string | Array<ResponseInputText | ResponseInputImage | ResponseInputFile>
    ```
    
    This change allows custom tool calls to return images, files, and rich text content in addition to plain strings, aligning `ResponseCustomToolCallOutput` with the broader `ResponseInput` type system. Because this alters the type and shape of the field, it may break existing callsites that only accept strings.
    
    BREAKING CHANGE: `ResponseFunctionToolCallOutputItem.output` and `ResponseCustomToolCallOutput.output` now return `string | Array<ResponseInputText | ResponseInputImage | ResponseInputFile>` instead of `string` only. This may break existing callsites that assume `output` is always a string.
    stainless-app[bot] committed Sep 30, 2025
    Configuration menu
    Copy the full SHA
    4de5afd View commit details
    Browse the repository at this point in the history
  3. release: 6.0.0

    stainless-app[bot] committed Sep 30, 2025
    Configuration menu
    Copy the full SHA
    08ddfb4 View commit details
    Browse the repository at this point in the history
Loading