868a7497d0
## What this PR does Fixes an issue where backport releases incorrectly became marked as "Latest" despite passing `make_latest: 'false'` to the GitHub API. **Root cause:** The `getLatestRelease()` API returns the release with the "Latest" flag, not the highest semver version. Combined with race conditions during parallel release publishing and GitHub API potentially ignoring `make_latest: 'false'`, backport releases were incorrectly marked as latest. **Solution:** - Replace `getLatestRelease()` with semver-based max version detection across all published releases - After publishing a backport release, explicitly restore the latest flag on the highest semver release - Remove unused dead code from `tags.yaml` workflow ### Release note ```release-note [ci] Fix latest release detection to use semver comparison instead of GitHub's "Latest" flag ``` |
||
|---|---|---|
| .. | ||
| auto-release.yaml | ||
| backport.yaml | ||
| pre-commit.yml | ||
| pull-requests-release.yaml | ||
| pull-requests.yaml | ||
| retest.yaml | ||
| tags.yaml | ||
| update-releasenotes.yaml | ||