Publish Linux runtime wheels with glibc-compatible tags#21812
Publish Linux runtime wheels with glibc-compatible tags#21812aibrahim-oai wants to merge 1 commit into
Conversation
85b22dc to
11e31d7
Compare
|
This change is part of the following stack:
Change managed by git-spice. |
becbd2a to
284b1ee
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 284b1eea87
ℹ️ 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".
| platform_tag="musllinux_1_1_aarch64" | ||
| ;; | ||
| x86_64-unknown-linux-musl) | ||
| platform_tag="musllinux_1_1_x86_64" |
There was a problem hiding this comment.
Use glibc-compatible Linux wheel tags
These Linux runtime wheels are tagged musllinux_*, so pip on normal glibc Linux hosts will not consider them compatible and cannot satisfy the SDK's pinned openai-codex-cli-bin dependency. The bundled Rust binaries are MUSL-linked release artifacts intended to run on glibc too, so publish them with a compatible Linux tag instead of limiting installs to musl/Alpine.
Useful? React with 👍 / 👎.
Co-authored-by: Codex <noreply@openai.com>
284b1ee to
4df5670
Compare
Why
The Python SDK depends on
openai-codex-cli-binruntime wheels being installable on the Linux hosts our users actually run. The release workflow currently tags the Linux runtime artifacts asmusllinux_*, which makes pip ignore them on normal glibc distributions even though the bundled Rust executables are intended to run there.What changed
manylinux_2_17_aarch64andmanylinux_2_17_x86_64instead ofmusllinux_1_1_*.Verification
manylinuxvsmusllinux.mainthrough the merged stack.Follow-up
After publishing the next alpha from this branch, install the SDK/runtime in a fresh glibc Linux environment and confirm pip resolves the tagged Linux wheel as expected.