Consider cibuildwheel for building wheels?
Disclaimer: I haven't been involved recently in maintaining our wheel building infrastructure, so I don't know how well it is working or not. But, I recently had a [good experience](https://github.com/pygeos/pygeos/blob/64af221b02a8fba2dbe28de5702b01afcb045306/.github/workflows/release.yml#L39) with cibuildwheel with a relatively complex package, so therefore thought to bring it up.

Cibuildwheel (https://cibuildwheel.readthedocs.io/en/stable/) is a package helping to build wheels for all different platforms and architectures  / python versions on your CI of choice (they support most of the common CI services). And if using GitHub Actions, you can build all wheels with a single CI service.

Scikit-learn started to use it last year (https://github.com/scikit-learn/scikit-learn/pull/17921). You can see their github workflow as an example: https://github.com/scikit-learn/scikit-learn/blob/main/.github/workflows/wheels.yml (this single workflow config includes building all the wheels, building the sdist, and uploading them to the anaconda wheelhouse for nightly builds). 
(cc @ogrisel @thomasjpfan in case you have feedback on how the switch worked out)

And it seems numpy also started considering this: https://github.com/numpy/numpy/pull/20102 
Another example mentioned in the dev meeting: https://github.com/googleapis/python-crc32c/blob/b1a8d14bf0a1b4f1faa0f9fdd4307e15699daeff/.github/workflows/python-publish.yml#L245

Some potential advantages:

- Easier to maintain (no issues with Travis credits, be able to do everything with a single CI, easier to support all architectures and new python versions, no need to synchronize with a different repo, ..)
- Having it in the repo here also allows triggering the builds on a PR on demand, if a PR would influence wheel building (I wouldn't enable the workflow by default for every PR).

cc @simonjayhawkins @lithomas1 since you are the ones mostly working on https://github.com/MacPython/pandas-wheels, it's of course mostly up to you to decide (and even if the end result might be better, every migration also has a cost).

