FTR, GitHub Actions artifacts (as I know) could not be downloaded by not logged users (e.g. there are no anonymous downloading for GitHub Actions artifacts).

I may be wrong.

You are correct (I think they do it to avoid excessive bandwidth costs). This isn't a huge problem though since we can publish a rolling "nightly" pre-release, like wasmtime does. So the artifacts would be published as assets like here.

There's an upstream action for snapcraft: https://github.com/snapcore/action-build and it seems like arm64 and amd64 are both supported.

So this seems like a good idea, snap-wise.

@whitequark you had mentioned that the current build are debug anyway, so not suitable for general use. Would this change include producing release builds?

Either way, if it makes life easier I say do it.

Would this change include producing release builds?

We could far more easily set it up so that e.g. after debug builds succeed and go through testing, there is another round of release builds that are uploaded for general use. You can kind of do this with Travis/Appveyor but it's a huge pain with those.

I must correct my statement regarding arm64 support: the only way to build on arm64 seems to self-hosted runners. Github-hosted runners are only amd64 as far as I can see (https://github.community/t/does-github-actions-support-multiple-os-architectures/16526).

Closing because it looks like we're going with Travis for now.

We can come back to this if necessary. Travis has its own problems, but it's a) there and b) has brittle arm64 support as a USP.