Fix wheel naming convention#4
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Remove the rename step that appended -amd64/-arm64 to wheel filenames. The platform is already encoded in the standard wheel name (linux_x86_64 vs linux_aarch64), and the suffix breaks pip/uv parsing.
Note
Low Risk
Only changes CI packaging output naming; no runtime code changes, with limited impact beyond release artifacts.
Overview
Removes the GitHub Actions step that renamed built wheels to add a custom
-amd64/-arm64suffix before upload.Wheels are now uploaded to artifacts and GitHub Releases using the standard wheel filename produced by
python -m build, improving compatibility with tooling that parses wheel tags.Written by Cursor Bugbot for commit 5573909. This will update automatically on new commits. Configure here.