* ci: keep lotus checkout clean in the release workflow
* ci: allow providing custom ref to the release workflow
* ci: fix version check performed during the release
* ci: fix install go step of the release workflow
* ci: fix the working directory for the install go step in release workflow
* ci: provide github ref to lotus scripts explicitly
* ci: use actions from the chosen ref in release workflow
* ci: fix install go in release workflow
* ci: fix artifact upload in release workflow
* ci: set INPUTS_REF variable in release workflow
* ci: fix publish checksums script
* ci: allow releasing docker from an arbitrary ref
* ci: fix docker channel discovery
This is a small refactor of our workflow to test out goreleaser, a yaml
based tool for building, packaging, and releasing go binaries on
multiple platforms. It supports building binaries for to most of the platforms we
care about, including linux and macos, and also supports publishing
those binaries automatically as releases in Github, homebrew, snap, and
even apt / deb.
If this trial goes well, I think we should eventually replace the entire
release workflow with goreleaser. For now, this test is more tightly
scoped to only automated the MacOS release process, since that is the
one we have the most issues with. This PRi / commit:
- Builds darwin-amd64 and darwin-arm64 binaries of lotus, lotus-miner,
and lotus-worker
- Packages them into a universal darwin binary
- Publishes those to a release in Github based on the current tag
- Uses the binaries in the release to auto-publish and updated homebrew
configuration to filecoin-project/homebrew-lotus
- Does a `dry-run` build to produce a snapshot on release branches with
no tag
- Manually generate and upload checksums after goreleaser
