`cargo release` for releasing the coreutils
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
Instead of our custom script for tagging and publishing releases, I think we should use cargo release (or some other similar tool). However, I think there's a small problem with cargo release at the moment which is that it cannot work around the rate limits of crates.io. They only do a check that you're not going to hit the rate limit, but of course we will always hit the rate limit with ~100 crates.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the custom script currently used to tag and publish releases, then compare its behavior with cargo release. Investigate cargo release's handling of crates.io rate limits for the project's roughly 100 crates. Done means an agreed release-tool approach that can publish all crates reliably without exceeding those limits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- release
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100