[Bug]: The "latest" GitHub Release label should always be the later release of the latest Salt major version
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
What happened?
At the moment, when a new Salt release occurs, it automatically becomes the latest release.
This can mean that 3008.2 doesn't get labeled and displayed as the latest release on the repository is a new release happens for 3006.x or if a limited/isolated patch release happens for a previous minor version (ex. 3008.1-1).
Release logic should verify if the current release is a higher major and minor version that the previous latest labeled release, otherwise, a release should happen and not get the new label.
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 locating the release logic that assigns the GitHub "latest" label; the issue names no file, test, or entry point. Trace how the current release is compared with the previous latest release, then verify behavior for a newer major/minor release and for an isolated patch release on an older minor line.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100