CI: Add cibuildwheel GitHub Actions workflow

[matthewfeickert]

• Add GitHub Actions based workflow that uses cibuildwheel to build wheels for target platforms.
• Add upload of wheels to PyPI on publish using Trusted Publishers.

This workflow copies heavily from the one @henryiii setup for https://github.com/scikit-hep/boost-histogram.

Addresses following components of Issue #104:

• setup cibuildwheel to build the full matrix of wheels so users don't have to have a compiler installed
• setup PyPI trusted publisher to automate releases (will require @tacaswell to do this on the PyPI side)

Requires PR #107 to go in first.

[matthewfeickert]

@tacaswell this is ready for review now (thanks for merging PR #107).

[matthewfeickert]

👋 Ping @tacaswell.

[peterfarrell]

This would be welcome improvement for us.

[tacaswell]

I'll sort out the pypi side and merge this in the next week.

[matthewfeickert]

I'll sort out the pypi side and merge this in the next week.

@tacaswell sounds good and thanks!

For the last remaining bit after that in Issue #104

setup automatic version number based on tags

I think this can be done similarly to how we're doing things in https://github.com/scikit-hep/scikit-hep-testdata and https://github.com/scikit-hep/boost-histogram, which is just to use purefly dynamic version metadata.

[matthewfeickert]

👋 @tacaswell just pinging on this in 2026 to remind us both of this. Let me know if there is anything that is needed on my side that I can do to help. 👍

[tacaswell]

@matthewfeickert Can you point me to docs on what I need to do on the pypi side?

[peterfarrell]

@tacaswell It looks like there is a "upload if release" CI job that was skipped in the last run of the workflow.

Looks like the trigger rule is:

if: github.event_name == 'release' && github.event.action == 'published'

It appears creating a new Release (and Git tag) in GH and then using "Publish Release" would trigger this workflow.

[matthewfeickert]

Can you point me to docs on what I need to do on the pypi side?

@tacaswell Sure. You want the Adding a Trusted Publisher to an existing PyPI project PyPI docs.

[matthewfeickert]

It appears creating a new Release (and Git tag) in GH and then using "Publish Release" would trigger this workflow.

@peterfarrell That's correct, except with less steps. After the Trusted Publisher has been setup on PyPI to allow for publishing through short lived tokens, then to create a release a GitHub Release

datrie/.github/workflows/wheels.yaml

Lines 8 to 10 in 142eef5

	release:
	types:
	- published

should be made to trigger

datrie/.github/workflows/wheels.yaml

Line 119 in 142eef5

if: github.event_name == 'release' && github.event.action == 'published'

No additional actions are needed.

[peterfarrell]

@matthewfeickert could I assist with getting Trusted Publisher setup so a release can be made? LMK what I can do to assist.

[matthewfeickert]

could I assist with getting Trusted Publisher setup so a release can be made? LMK what I can do to assist.

@peterfarrell I don't have permissions on PyPI to setup trusted publishers, so we'll need a project maintainer to do that. So I believe that's @kmike and @tacaswell.