The time has come for replacing Travis CI with GitHub Actions.
This is because Travis CI, which we use for "Continuous Integration" (i.e. "tests"), has changed it's pricing model to be less favourable for Open Source projects like ours. At the same time "GitHub Actions" has matured a lot, and can perform all the same things as Travis CI could. At the same time, it is fully integrated into GitHub and we can get rid of a third-party dependency.
Another positive thing is that Mac OSX testing seems much better supported on GitHub Actions.
The time has come for replacing Travis CI with GitHub Actions.
This is because Travis CI, which we use for "Continuous Integration" (i.e. "tests"), has changed it's pricing model to be less favourable for Open Source projects like ours. At the same time "GitHub Actions" has matured a lot, and can perform all the same things as Travis CI could. At the same time, it is fully integrated into GitHub and we can get rid of a third-party dependency.
Another positive thing is that Mac OSX testing seems much better supported on GitHub Actions.