[codex] Pin Python SDK to runtime 0.137.0a4#26216
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f56746d37a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "Topic :: Software Development :: Libraries :: Python Modules", | ||
| ] | ||
| dependencies = ["pydantic>=2.12", "openai-codex-cli-bin==0.136.0"] | ||
| dependencies = ["pydantic>=2.12", "openai-codex-cli-bin==0.137.0a4"] |
There was a problem hiding this comment.
Update the frozen lockfile with the runtime pin
This changes the SDK requirement to openai-codex-cli-bin==0.137.0a4, but sdk/python/uv.lock still records the project metadata and locked package as 0.136.0 (requires-dist and the package entry). I checked .github/workflows/sdk.yml and .github/workflows/python-sdk-release.yml; both run uv sync --extra dev --frozen, and uv sync --help says --frozen syncs without updating uv.lock, so CI/release will refuse to reconcile this pyproject/lock mismatch (or keep using the stale runtime) until the lockfile is refreshed in the same change.
Useful? React with 👍 / 👎.
| [tool.uv] | ||
| exclude-newer = "7 days" | ||
| exclude-newer-package = { openai-codex-cli-bin = "2026-06-01T20:00:00Z" } | ||
| exclude-newer-package = { openai-codex-cli-bin = "2026-06-03T03:00:00Z" } |
There was a problem hiding this comment.
Set exclude-newer after the runtime upload time
When the new runtime is published after this commit, this package-specific cutoff will still limit openai-codex-cli-bin candidates to uploads before 2026-06-03T03:00:00Z (the same value is repeated under [tool.uv.pip]). uv lock --help describes exclude-newer as limiting candidates to packages uploaded prior to the given date, so the future 0.137.0a4 upload would remain invisible to uv even after it exists, preventing the lock refresh and frozen CI from resolving the pinned version.
Useful? React with 👍 / 👎.
Summary
openai-codex-cli-bin==0.137.0a4rust-v0.137.0-alpha.4sdk/python/uv.lockwith all eight published runtime wheelsRuntime publication
openai-codex-cli-bin==0.137.0a4through thepython-sdk-releaseworkflowValidation
just fmtrust-v0.137.0-alpha.4release wheeluv lock --check --default-index https://pypi.org/simple