killercup / killercup/cargo-edit
Binary builds for each release?
- Dominant language
- Rust
- Stars
- 3.5k
- Forks
- 166
- PR merge metrics
- No merged PRs in 30d
Description
I'm looking to use cargo-edit in some internal automation tooling to bump versions, cut releases, etc. For that kind of workflow, a `cargo install` is a bit more awkward than it is when installing a tool for personal use. Ideally, we'd just be able to pull down a tarball with precompiled x86_64-unknown-linux-musl binaries.
Do you have any interest in supporting that? I can look into making the GHA changes if so!
Contributor guide
Research direction
No files or tests are named. Start by reviewing the existing GitHub Actions release configuration and the cargo-edit release process; identify how an x86_64-unknown-linux-musl artifact would be packaged and published, then verify that a release provides a downloadable tarball with the precompiled binary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- ci-cd, cli, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100