You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 85bb536
Browse filesBrowse the repository at this point in the historyBrowse files
feat(api): keep callable API keys scoped to each request (#4216)
## Summary
Keeps each callable API-key result with its own HTTP request or
WebSocket connection, including Azure API-key authentication.
## Changes
- Keep overlapping requests from using another request's callable
API-key result.
- Preserve explicit authentication headers, request-preparation hooks,
retries, and cached key visibility.
- Pass the resolved Azure API key into each Realtime connection.
Public signatures, header precedence, retries, and cached key visibility
stay compatible. Private `_auth_headers` overrides may need updates
because prepared credentials take precedence. Overrides of
`_configure_realtime` must accept the new `api_key` keyword. This change
targets a minor release under the README's [internal-interface
policy](https://github.com/openai/openai-python#versioning).
Validation includes 55 credential and runtime-binding regression tests
under both Pydantic 1 and 2, plus 28 release and mixed-version wire
checks. The wire checks include the generated caller with the v3.41.0
runtime. Canonical lint passes. The generated source change is limited
to Realtime; no workflows change.
Public CI passes: 17 checks passed and 9 were skipped. SDK-owner
approval and the exact merge-conflict check are complete. All 109
required compiler targets have passing results; one TypeScript shard
passed on rerun after its process was killed.
Co-authored-by: markstuart-oai <323302876+markstuart-oai@users.noreply.github.com>
0 commit comments