cibuildwheel: update workflow

[xavier2k6]

• Bumped cibuildwheel action
• Removed macos-12 runner (deprecated)
• Updated Boost Download URL
• Used more appropriate OS Runners for required jobs (architecure specific)
• Explicitly declare each cibuildwheel identifier

[xavier2k6]

@qstokkink I've done a dry-run for all python versions from python 3.9+ across all builds so that the tribler team can test/use them especially for requested macOS 12 prior to it's imminent deprecation/removal as a GH runner image. (Today - 3rd Dec is it's deadline....)

I plan on removing macos-12 when it's completely unavailable as a GH runner image from this PR.

[qstokkink]

@xavier2k6 Thanks 🙏 I had hoped for a PyPI release before the deadline, but I guess that wasn't in the cards.

[xavier2k6]

I plan to do a re-base/one final change after your macos fixes are in-place.....unsure of why windows-2025 is failing & don't really have time to look into it. (will more than likely revert to windows-latest which is currently = windows-2022)

[xavier2k6]

@arvidn should we sync below files with upstream??
https://github.com/arvidn/libtorrent/blob/RC_2_0/tools/cibuildwheel/manylinux/build-openssl.sh
https://github.com/arvidn/libtorrent/blob/RC_2_0/tools/cibuildwheel/manylinux/build_utils.sh

Upstream:
https://github.com/pypa/manylinux/blob/main/docker/build_scripts/build-openssl.sh
https://github.com/pypa/manylinux/blob/main/docker/build_scripts/build_utils.sh

---

Unsure, if below needs to be updated at some stage:
https://github.com/arvidn/libtorrent/blob/RC_2_0/tools/cibuildwheel/manylinux/openssl-version.sh

[arvidn]

I think the condition for this job needs to be updated to also cover CIBW_BUILD ending with "win_amd64"

[arvidn]

or maybe instead look at whether os starts with "windows-"

[xavier2k6]

The win_amd64 build had no issues previously with windows-2022...I'll think I'll just revert to that as the windows-2025 image is still classed as beta & there are still tools etc. been added/updated. (will look in to using it again in a few weeks when v3 of cibuildweel action is released.)

Could also look at updating (manylinux) to build with FORTIFY_SOURCE=3 instead of 2

Is that ok with you??

[arvidn]

sure

[xavier2k6]

I'll rebase/make changes in about an hour or so.

[xavier2k6]

Thoughts on sync? -> #7805 (comment)

[arvidn]

#7824

[arvidn]

@arvidn should we sync below files with upstream?? https://github.com/arvidn/libtorrent/blob/RC_2_0/tools/cibuildwheel/manylinux/build-openssl.sh https://github.com/arvidn/libtorrent/blob/RC_2_0/tools/cibuildwheel/manylinux/build_utils.sh

Upstream: https://github.com/pypa/manylinux/blob/main/docker/build_scripts/build-openssl.sh https://github.com/pypa/manylinux/blob/main/docker/build_scripts/build_utils.sh

Yeah, that would seem reasonable. There's a tools/cibuildwheel/manylinux/update-scripts.sh that might do that

[xavier2k6]

@arvidn re-based & as you can see both manylinux builds are passing.....should I add the manylinux script changes here too or do you want to do your own thing?

[arvidn]

CI seems very finicky when changing these things. so any green CI I think should land without mixing in additional risks of all the errors I've seen in the other PR

[arvidn]

thanks!