Repository navigation
build: PyPI release workflow with abi3 wheels for 5 platforms - #7
Merged
Merged
Conversation
- release.yml builds abi3 wheels (Python >= 3.9) for linux x86_64/aarch64 (manylinux_2_28), macOS arm64/x86_64 and Windows x86_64, plus an sdist. Each runnable wheel is installed and tested on Python 3.9 and 3.13. Pushing a vX.Y.Z tag (checked against Cargo.toml) publishes to PyPI via trusted publishing; PRs touching packaging build + test only. - Enable pyo3 abi3-py39: one wheel per platform instead of per Python. - License files now match the declared MIT OR Apache-2.0 (the GPL-3.0 LICENSE file contradicted pyproject and README). - Full PyPI metadata (PEP 639 license expression, readme, urls, classifiers); version comes from Cargo.toml only. - Commit Cargo.lock; release builds use --locked. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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
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.
Summary
Makes
pip install burn-pythonpossible..github/workflows/release.ymltests/test_ops.pyon Python 3.9 and 3.13 (macOS x86_64 is cross-compiled on arm64, so it's build-only).vX.Y.Ztag publishes to PyPI via trusted publishing (no API token stored); the tag is checked againstCargo.toml's version first.pyo3/abi3-py39): checked locally — the same wheel imports and passes the op tests on Python 3.9 and 3.13, flex and wgpu.LICENSEwas GPL-3.0 whilepyproject.tomland the README said MIT OR Apache-2.0. NowLICENSE-MIT+LICENSE-APACHE(canonical text from apache.org), matching Burn.Cargo.tomlonly.Cargo.lockcommitted, release builds use--lockedso wheels are reproducible.Before the first release (one-time, on pypi.org)
Add a pending trusted publisher for project
burn-python: ownerasjad2401, repoburn-python, workflowrelease.yml, environmentpypi. Thengit tag v0.1.0 && git push origin v0.1.0.🤖 Generated with Claude Code