Since semantic-release-rust takes a few minutes to compile, Would you be in favor of adding release builds to the Github releases? Such a feature would have the following advantages:
CI builds do not have to compile semantic-release-rust every time they run.
cargo binstall support is feasible.
I was taking a look at @semantic-release/github and it appears that it natively supports added extra assets to the Github release via the .releaserc.
Necessary changes:
Add the asset paths to the .releaserc (as defined here)
Make the existing CI build release binaries for Linux, MacOS, and Windows.
Place each/all the binaries in a tarball for upload.
Since
semantic-release-rust
takes a few minutes to compile, Would you be in favor of adding release builds to the Github releases? Such a feature would have the following advantages:semantic-release-rust
every time they run.cargo binstall
support is feasible.I was taking a look at
@semantic-release/github
and it appears that it natively supports added extra assets to the Github release via the.releaserc
.Necessary changes:
.releaserc
(as defined here)