Skip to content

dev/release: do not create GitHub release if release is old

Warren Gifford requested to merge release/do-not-create-old-releases into main

Created by: bobheadxi

The recent 3.35.2 patch release shows up as the latest release, as reported by @eseliger :

image

So apparently GitHub just treats whatever release was published most recently as latest, which is kind of right but also doesn't feel like the way it should work but oh well 😅 https://github.community/t/latest-release-isnt-the-real-latest/2244/6

This change adds an additional check to see if the latest release is newer than the release being published and if it is, we don't publish a GitHub release for it. I think this is fine because folks watching the repo are likely watching for the latest and greatest, not a patch fix to an older release. I think?

Merge request reports

Loading