Skip to content

fix release#2759

Merged
awni merged 1 commit intomainfrom
fix_release
Nov 13, 2025
Merged

fix release#2759
awni merged 1 commit intomainfrom
fix_release

Conversation

@awni
Copy link
Copy Markdown
Member

@awni awni commented Nov 13, 2025

A few changes here:

  • Use conda python for release builds so that we don't have the issue of the python binary being compiled on a later macos than the target for the build (as we had it in circle ci)
  • Remove releases to test pypi as they are not useful
  • Add support dev release as we had it in circle ci
  • Test on more than one macos version as we had it in circle ci (now test on 14 and 15)

@awni awni requested a review from angeloskath November 13, 2025 20:20
@awni awni force-pushed the fix_release branch 2 times, most recently from f508909 to 134af5b Compare November 13, 2025 20:47
Copy link
Copy Markdown
Member

@angeloskath angeloskath left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@awni awni merged commit b65f882 into main Nov 13, 2025
9 checks passed
@awni awni deleted the fix_release branch November 13, 2025 23:34
- uses: ./.github/actions/setup-macos
- uses: ./.github/actions/build-macos
with:
macos-target: ${{ matrix.macos-target }}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this more useful than setting an env for the entire step?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By no means, I'd rather set it for the full step, just didn't know it was possible.

run: |
uv run --no-project setup.py clean --all
MLX_BUILD_STAGE=2 uv run -m build -w
conda activate env
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Conda needs to be set up for nightlies as well

@@ -54,6 +55,7 @@ jobs:
runs-on: ${{ matrix.runner }}
env:
PYPI_RELEASE: 1
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dos this need to be the opposite of DEV_RELEASE?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, PYPI_RELEASE is always on for this. And if DEV_RELEASE is also on it will do a dev release with a dev tag included.

repository-url: ${{ needs.setup.outputs.pypi_url }}
skip-existing: ${{ needs.setup.outputs.skip_duplicates }}
print-hash: true
repository-url: https://upload.pypi.org/legacy/
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the default and doesn’t need to be set

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.

3 participants