In the process of transitioning to the new CI, I noticed one interesting difference in the way numba-cuda publishes packages (.github/workflows/publish.yaml). Here is the main difference vs cuda-python:
- numba-cuda:
- release on tagging
- always rebuild wheels when the release workflow is triggered
- also builds sdist
- cuda-python
- release triggered manually on GitHub web UI
- avoid rebuilding wheels and instead grab the wheels from the GitHub Artifacts associated with the commit/tag
- do not ship sdist
Because of the rebuilding requirement, I was not able to remove the build workflows. We should decide if we want to unify this bit of the CI.
In the process of transitioning to the new CI, I noticed one interesting difference in the way numba-cuda publishes packages (.github/workflows/publish.yaml). Here is the main difference vs cuda-python:
Because of the rebuilding requirement, I was not able to remove the build workflows. We should decide if we want to unify this bit of the CI.