I don't want this to be permanent, but having any ❌ makes it hard to know (quickly) if we're making things better or worse.

If we can get non-static builds happy (which I think we are), we can then reenable static builds and go through the process to get the builds clean.

Seems fine. I'd love to move away from Travis to GitHub Actions. Travis is probably on life support and GitHub supports Windows builds so we don't need to separately maintain AppVeyor or whatever we're using.

@rgov agreed! That's high-up on my list of things I'd like to look at (otherwise, there's an element of "building on a foundation of sand").