release: 6.46.0#1959
Merged
apcha-oai merged 2 commits intoJul 9, 2026
Merged
Conversation
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next--components--openai
branch
from
03718d1 to
573a09f
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next--components--openai
branch
from
573a09f to
a0d4041
Compare
OkTest Summary❌ Failed for Node SDK PR #1959. SDK merge ( |
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next--components--openai
branch
from
a0d4041 to
4371fcc
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next--components--openai
branch
from
4371fcc to
45d5095
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next--components--openai
branch
from
45d5095 to
01792d8
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next--components--openai
branch
from
01792d8 to
9a22b04
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next--components--openai
branch
from
9a22b04 to
13e1dd4
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next--components--openai
branch
from
13e1dd4 to
1876dfd
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next--components--openai
branch
from
1876dfd to
8a7ec04
Compare
apcha-oai
approved these changes
Jul 9, 2026
Contributor
Author
|
🤖 Release is at https://github.com/openai/openai-node/releases/tag/v6.46.0 🌻 |
HAYDEN-OAI
added a commit
to openai/openai-agents-js
that referenced
this pull request
Jul 9, 2026
## Summary - Type the Chat Completions usage adapter as Agents SDK `UsageInput` instead of the generated Responses API `ResponseUsage`. - Bump the workspace's direct `openai` dependencies to `^6.46.0` across the published packages and examples, and regenerate package metadata. - Add a version-specific `minimumReleaseAgeExclude` for `openai@6.46.0` so the just-published launch SDK can pass the repository's normal frozen install policy. - Add patch changesets for `@openai/agents`, `@openai/agents-core`, and `@openai/agents-openai`. ## Why [openai/openai-node#1959](openai/openai-node#1959) shipped `openai@6.46.0` with the required `cache_write_tokens` field on `ResponseUsage.InputTokensDetails`. The downstream Agents SDK regression check failed with TS2741 because `toResponseUsage()` synthesizes an Agents usage object containing only `cached_tokens`, while its return annotation incorrectly required the full Responses API output schema. The value is immediately passed to `new Usage(...)`, whose supported input boundary is `UsageInput`. Using that type removes the accidental coupling to generated API output fields and lets required Responses outputs remain required. The dependency floor and workspace examples now all use 6.46 so TypeScript does not load nominally incompatible `OpenAI` classes from 6.44 and 6.46 in the same build. The cooldown exception is scoped to exactly `openai@6.46.0`, not the package generally. ## Impact There is no runtime behavior change in the usage adapter. Published Agents packages now require `openai@^6.46.0`, and the workspace explicitly validates against the GPT-5.6 launch SDK. ## Validation - `pnpm changeset:validate-prompt` (patch bumps validated) - `pnpm install --frozen-lockfile` (normal supply-chain policy passed) - `bash .agents/skills/code-change-verification/scripts/run.sh` - Reproduced the original downstream check with the built SDK from openai/openai-node#1959 linked into a scratch checkout: - `pnpm build` - `pnpm lint` - `pnpm docs:scripts:check`
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated Release PR
6.46.0 (2026-07-09)
Full Changelog: v6.45.0...v6.46.0
Features
Bug Fixes
Documentation
This pull request is managed by Stainless's GitHub App.
The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.
For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.
🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions