This completes the move to GitHub actions, disabling the usage of appveyor. The workflow paradigm is nicer (as I can have a workflow just for publishing when a release is made) than appveyor's all-in-one approach, and it is less flaky in that appveyor would randomly kill running builds due to the query method taking a bit of time.
The syntax for writing a workflow is also a bit nicer in my opinion, and at least compared to the old appveyor set-up, we are using GH to test against a much wider range of node and db versions.
This completes the move to GitHub actions, disabling the usage of appveyor. The workflow paradigm is nicer (as I can have a workflow just for publishing when a release is made) than appveyor's all-in-one approach, and it is less flaky in that appveyor would randomly kill running builds due to the query method taking a bit of time.
The syntax for writing a workflow is also a bit nicer in my opinion, and at least compared to the old appveyor set-up, we are using GH to test against a much wider range of node and db versions.