When we create a new SEMVER formatted git tag, then travis will kick in
and run Goreleaser to create our binaries, checksums, and signatures
and upload them to a new GitHub release.
I loaded a GPG key into Travis and 1Password Dev vault to be used to sign the releases.
Part of https://aptible.atlassian.net/browse/DP-299
Follows Hashicorp advice in: https://www.terraform.io/docs/registry/providers/publishing.html#creating-a-github-release
When we create a new SEMVER formatted git tag, then travis will kick in and run Goreleaser to create our binaries, checksums, and signatures and upload them to a new GitHub release.
I loaded a GPG key into Travis and 1Password Dev vault to be used to sign the releases.
Example release for review is v0.0.0-pre: https://github.com/aptible/terraform-provider-aptible/releases I'll remove that release and tag once this PR is approved.