⚠️ Need to sort out PR #290 first (included here so that all tests pass)
The contribution of this PR is commit fef816569c05c43a715bbbd9660091cc5a42bae7
This PR proposes to add github actions workflow to build the wheels and tarball and deploy them to pypi.
The workflow builds wheels for windows (x86_64), macos (x86_64 and arm64) and linux (x86_64, ppc64le and aarch64) using cibuildwheel.
This workflow can be run manually and is run automatically when creating a "release" through github.
When the workflow is started from a "release", the created tarball and wheels are uploaded to pypi, if: build and tests are successful and the deployment is manually approved (This still needs some setup on both pypi and github side, but it's no big deal).
⚠️ Need to sort out PR #290 first (included here so that all tests pass)
The contribution of this PR is commit fef816569c05c43a715bbbd9660091cc5a42bae7
This PR proposes to add github actions workflow to build the wheels and tarball and deploy them to pypi. The workflow builds wheels for windows (x86_64), macos (x86_64 and arm64) and linux (x86_64, ppc64le and aarch64) using cibuildwheel.
This workflow can be run manually and is run automatically when creating a "release" through github. When the workflow is started from a "release", the created tarball and wheels are uploaded to pypi, if: build and tests are successful and the deployment is manually approved (This still needs some setup on both pypi and github side, but it's no big deal).
Here is a run of this workflow: https://github.com/t20100/hdf5plugin/actions/runs/7639984937/job/20815940046
closes #286