obophenotype / obophenotype/uberon
Versioning mismatch
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Emacs Lisp
- Stars
- 163
- Forks
- 43
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 5
Description
Uberon term
All collection
Bug description
I am not sure if that is the case for the rest of the releases, but we noticed that the release tag for v2026-06-23 is not consistent with the version mentioned in the file v2026-06-19 at uberon.json
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 comparing the v2026-06-23 release tag with the version recorded in uberon.json at v2026-06-19. Check whether the mismatch also occurs in other releases, as the issue asks about the broader release history. Done means the release tag and the version recorded in uberon.json are consistent.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100