Build wheels for musl aarch64 (aka ARM) Linux (musllinux_1_1_aarch64)

[bwoodsend]

Addresses #476 (comment).

Changes proposed in this pull request:

• Add musl aarch64 wheels to the build matrix.

[codecov-commenter]

Codecov Report

Merging #478 (f4d8d75) into main (1dda667) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #478   +/-   ##
=======================================
  Coverage   88.96%   88.96%           
=======================================
  Files           6        6           
  Lines        1685     1685           
=======================================
  Hits         1499     1499           
  Misses        186      186           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1dda667...f4d8d75. Read the comment docs.

[bwoodsend]

Hmm, commit number 2 (ce972b4) doesn't appear to be doing anything. I guess paths: and branches: must both be satisfied rather than one or the other must be satisfied as I'd hoped. I'll drop it then enable that workflow in a throwaway branch so we can see if it works or not.

[bwoodsend]

Actually could we add workflow_dispatch: instead for one-off triggering? It would add a trigger this workflow button we can use whenever we want to work on this file without merging it into the main branch.

[hugovk]

paths needs to be under an event.

https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#example-including-paths

Maybe something like this?

 on:
   push:
     branches:
       - main
+  pull_request:
+    paths:
+      - ".github/workflows/deploy-wheels-linux.yml"
+      - "scripts/build-manylinux-wheels.sh"
   release:
     types:
       - published

[hugovk]

Actually could we add workflow_dispatch: instead for one-off triggering? It would add a trigger this workflow button we can use whenever we want to work on this file without merging it into the main branch.

Sure, can do.

Do you think we'd need a guard so this only runs when it's on main?

      - name: Publish package to TestPyPI
        uses: pypa/gh-action-pypi-publish@master

[bwoodsend]

Do you think we'd need a guard so this only runs when it's on main?

Pull requests should lack access to the authentication secrets so I imagine that step will fail. So yes, probably.

[bwoodsend]

https://github.com/ultrajson/ultrajson/pull/478/checks?check_run_id=3651486517#step:11:15

Yep we do.

[bwoodsend]

The travis error just looks like an internet connection blip on their end. The url it was pulling exists and works. Safe to ignore?

[hugovk]

I'll hit restart on that one, but yep, safe to ignore Travis CI in this PR, we're not touching it.

[bwoodsend]

Travis is looking happier now!

[hugovk]

Thank you!