protocolbuffers / protocolbuffers/protobuf
[Ruby] google-protobuf source_code_uri uses nonexistent v4.x tags
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 72k
- Forks
- 16.3k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 140
Description
Summary
The Ruby gemspec derives source_code_uri from the gem version as v4.36.0/ruby, but repository release tags omit the Ruby major and use v36.0. The published 4.36.0 metadata URL therefore returns 404 while v36.0/ruby exists.
Proposed correction
Strip the gem-only 4. prefix before constructing release and release-candidate tag names. Candidate: 99ccfb60557675befc159ee0d058377b79d4e67c on current main (5b1c20741838b8359193b97895cb0ff35b4ecf79).
An isolated gemspec/URI model covers final and RC naming. The 4.36.0 release provenance resolves to annotated tag v36.0 / commit 3f17acbf7ffbda81db8be17505554c726e558bb2.
I used an AI coding assistant during source/package review and verification. I am opening an issue first because CONTRIBUTING requires a CLA for patches; no CLA was signed as part of this audit.
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 in the Ruby gemspec logic that constructs source_code_uri from the gem version, using candidate commit 99ccfb60557675befc159ee0d058377b79d4e67c as the reference point. Exercise the isolated gemspec/URI model for final and release-candidate versions; done means 4.36.0 resolves to v36.0/ruby and the corresponding release-candidate naming remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 84/100