Releases are triggered by code review

[BigLep]

Done Criteria

1. The release steps outlined in https://github.com/filecoin-project/filecoin-ffi#release-process can be followed without requiring manual clicking in the GitHub UI. Instead, releases should occur as a result of an approved PR.
2. The release description should be populated with the GitHub-generated release notes. (This repo doesn't have an accurate/updated CHANGELOG).

Why Important

The release process in https://github.com/filecoin-project/filecoin-ffi#release-process doesn't have any peer review. Mistakes can get made. Mistagging has happened in the past and can't be reverted. This is usually fixed by just doing another release, but this adds unnecessary confusion.

User/Customer

Maintainers

Notes

1. Releases should also be clear and not have a duplicate asset-dedicated release.

[BigLep]

This is being addressed by #473

[BigLep]

Now the work is in #475

[rjan90]

Closing as completed since: #475 has been merged, and we also fixed some follow-ups:

• ci: fix asset publishing in release check workflow #488
• feat: download release tarball from named release #492

A full release triggered by code-review was shipped here: #493