[codex] Add independent beta release for the Python SDK#24828
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 25aabfc35d
ℹ️ 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".
| fi | ||
|
|
||
| cd sdk/python | ||
| uv sync --extra dev --frozen |
There was a problem hiding this comment.
Run the SDK release build on a musl-compatible runner
For a python-v* tag this job runs on ubuntu-latest, but this uv sync installs the locked openai-codex-cli-bin==0.132.0 dependency before staging. The lockfile only contains macOS, Windows, and musllinux wheels for that package (sdk/python/uv.lock lines 310-319), so on Ubuntu/glibc uv reports that the distribution has no wheel for the current platform and the release workflow fails before publishing. Run this step in the same Alpine/musl environment used by the SDK CI, or avoid requiring the runtime wheel on the Ubuntu release runner.
Useful? React with 👍 / 👎.
| [project] | ||
| name = "openai-codex" | ||
| version = "0.131.0a4" | ||
| version = "0.1.0b1" |
There was a problem hiding this comment.
Keep the Python SDK version monotonic
Publishing the new beta as 0.1.0b1 makes it sort lower than the already-published SDK versions such as 0.131.0a4 under PEP 440, so users asking pip/uv for --pre openai-codex or for an upgrade will continue to receive the older 0.131.0a4 release instead of this independent beta. The SDK can pin an older runtime independently, but the SDK distribution version itself still needs to be greater than the existing releases (for example a new major/minor scheme that is monotonic) for the beta release lifecycle to be discoverable by normal package resolution.
Useful? React with 👍 / 👎.
…elease # Conflicts: # sdk/python/README.md
Why
openai-codexneeds a beta release lifecycle without requiring beta releases of its pinned runtime package. Previously, SDK staging rewrote its runtime dependency to the SDK version, which made an SDK-only beta impossible.What changed
0.1.0b1and pin it to published stableopenai-codex-cli-bin==0.132.0.python-v*tag workflow that builds and publishes onlyopenai-codexthrough PyPI trusted publishing.0.132.0is the newest stable runtime admitted by the checked-in dependency date fence and retains the Linux wheel family currently used by SDK CI.Release setup
Before pushing
python-v0.1.0b1, configure PyPI trusted publishing for theopenai-codexproject with workflowpython-sdk-release.yml, environmentpypi, and jobpublish-python-sdk.Validation
uv run --frozen --extra dev ruff check src/openai_codex scripts examples tests.github/workflows/python-sdk-release.ymlwith PyYAML.openai_codex-0.1.0b1-py3-none-any.whlandopenai_codex-0.1.0b1.tar.gz.openai-codex-cli-bin==0.132.0.