Skip to content

mlx: set PYPI_RELEASE=1 to avoid a dev version - #1935

Merged
luhenry merged 1 commit into
mainfrom
mlx
Sep 15, 2026
Merged

luhenry merged 1 commit into
mainfrom
mlx

Conversation

@luhenry

@luhenry luhenry commented Sep 14, 2026

Copy link
Copy Markdown
Member
  • Package: mlx (and mlx-cpu, built by the same workflow)

setup.py's get_version() only emits the clean tag version when PYPI_RELEASE=1; otherwise it always appends .devYYYYMMDD+<git-hash>, even when building from an exact, unpatched v0.32.2 checkout with no dirty-tree involved at all. Both mlx and mlx-cpu published so far as 0.32.2.dev20260914+1f8e74e instead of the clean 0.32.2.

Fix: export PYPI_RELEASE=1 in both the build_backend (mlx-cpu) and build_frontend (mlx) jobs.

License: OK, unchanged.

setup.py's get_version() only emits the clean tag version (e.g. 0.32.2)
when PYPI_RELEASE=1; otherwise it always appends .devYYYYMMDD+<git-hash>,
even when building from an exact, unpatched v0.32.2 checkout. Applies to
both the mlx frontend and mlx-cpu backend packages, which share the same
setup.py (published so far: 0.32.2.dev20260914+1f8e74e for both).
@luhenry
luhenry merged commit 8ad8e04 into main Sep 15, 2026
37 of 39 checks passed
@luhenry
luhenry deleted the mlx branch September 15, 2026 11:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant