-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix latest tag in GitHub releases #73
Labels
bug
Something isn't working
Comments
2 tasks
emmyoop
added
tech_debt
Behind-the-scenes changes, with little direct impact on end-user functionality
and removed
oss_tooling
labels
Aug 3, 2023
martynydbt
removed
the
tech_debt
Behind-the-scenes changes, with little direct impact on end-user functionality
label
Apr 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now, the "Latest" release is simply the chronologically latest release that is non-draft & non-prerelease. This means when we release a patch to an older version, it gets marked as lates in GitHub now.
Example
first release 1.5.0 -> marked correctly as
latest
now release 1.4.3 -> this is now incorrectly marked as
latest
We need to determine if this is the true latest and mark it as such when releasing.
For now the workaround is to go in and update the releases appropriately in the UI when releasing a patch to an older version.
Details
You can list and filter releases with the gh cli: https://cli.github.com/manual/gh_release_list
If the current release is the same minor version or less with a higher patch, it should be marked latest.
Never mark pre-releases or draft releases as latest
The text was updated successfully, but these errors were encountered: