feat(release): add automated binary releases #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses #1 (triggered by pushing a tag, e.g.
v0.1.0
)Tested here: https://github.com/orhun/rustycli/actions/runs/5680656969
Example artifacts: https://github.com/orhun/rustycli/releases/tag/v0.1.0-test2
A couple of notes:
Cargo.lock
from.gitignore
and committed it to the repo (needed for binary builds +--locked
flag)rustls
feature forreqwest
for easier cross-compilation (see OpenSSL error cross-rs/cross#510)CARGO_TOKEN
as secret before merge forcrates.io
releasesCHANGELOG.md
andRELEASE.md