You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Current Latest in GH
Version Being Released
Mark Version being released as latest
1.5.2
1.5.3
yes
1.5.2
1.4.8
no
1.5.2
1.6.0
yes
1.5.2
1.6.0b1
no
Never mark pre-releases or draft releases as latest
The text was updated successfully, but these errors were encountered:
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: