fix(ci): avoid NumPy source builds and duplicate HTTPX coverage - #3573
Conversation
jbeckwith-oai
left a comment
There was a problem hiding this comment.
Reviewed the exact head (73f5e4a). The per-interpreter universal NumPy locks, explicit Rye virtualenv cache keys, HTTPX2-only test path, and Release Please uv.lock wiring are consistent and keep the workflow direct. I also regenerated both Rye lockfiles, ran the Python support-policy check and full lint, and verified the exact-head CI matrix is green.
HAYDEN-OAI
left a comment
There was a problem hiding this comment.
Reviewed exact head 73f5e4a7661f2d4ee448af22e3f0c0336435d0f8. No substantive issues found: interpreter-specific Rye cache keys and invalidation, universal NumPy wheel selections, HTTPX/HTTPX2 and Pydantic v1/v2 coverage, required-check names, fork/release behavior, workflow permissions, and CodeQL coverage are consistent. Confirmed HTTPX2 improved from 10m42s to 2m12s and Python 3.14 from 8m37s to 1m53s. Release automation also propagated the version into uv.lock in #3575.
Automated Release PR --- ## [2.53.0](openai/openai-python@v2.52.1...v2.53.0) (2026-08-03) ### Features * **api:** Add gpt-5.5 and tool name/namespace to Responses types ([openai#3569](openai#3569)) ([dd1202d](openai@dd1202d)) ### Bug Fixes * **ci:** avoid NumPy source builds and duplicate HTTPX coverage ([openai#3573](openai#3573)) ([b58332f](openai@b58332f)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Justin Beckwith <jbeckwith@openai.com>
Root cause
uv.locklacked the Release Please marker needed to keep its SDK version current.Fix
uv.lockfor release updates.Results
Validated with lint, SDK builds, lockfile checks, and both HTTPX/HTTPX 2 suites under Pydantic 1 and 2.
Fixes SDK-221.