Sort releases by semver in the "Resolved In" version selector
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Problem Statement
In the version selector shown when resolving an issue in a specific release, releases currently default to publish date ordering rather than semantic versioning.
This causes visual confusion when older build numbers are published after newer ones - for example, a customer seeing release@1.0.0+144136 appear above release@1.0.0+144150 simply because the former was published more recently.
Solution Brainstorm
No response
Product Area
Releases
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
No file or test is named. Start by locating the version selector used when resolving an issue in a release and the code that orders its releases. Confirm the current publish-date ordering, then verify that the selector displays releases in semantic-version order, including build numbers such as 1.0.0+144136 and 1.0.0+144150.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100