Add Tags for all previous releases where possible
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 979
- Forks
- 181
- Avg merge
- 5m
- Merged PRs (30d)
- 4
Description
Following from #497 I know we've now started tagging future releases. I think cargo records the current commit SHA hash in a .carge_vcs_info.json file in the published compressed crate file so it might be possible to add tags for past releases also. I can go through each past release and collect the SHA hashes if we're interested in adding them as tags.
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
Review issue #497 and inspect the published compressed crate files for past releases, looking for the .carge_vcs_info.json SHA data mentioned here. Done means adding tags for past releases where SHA hashes can be collected and identifying releases that cannot be tagged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, rust
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100