Tags `v0.28.0` and `0.28.0` both exist, pointing at different commits
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3k
- Forks
- 386
- Avg merge
- 1h 43m
- Merged PRs (30d)
- 1
Description
See https://github.com/mozilla/cbindgen/releases/tag/v0.28.0 and https://github.com/mozilla/cbindgen/releases/tag/0.28.0
It looks like the v-prefixed tag was made on the release branch, but the commit it's attached to wasn't retained when that branch was landed.
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
Compare the commits referenced by the v0.28.0 and 0.28.0 release links, and review the issue context about the release branch. Determine which tag should represent the release and reconcile the duplicate tags; done means the release tags no longer point to different commits.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100