Andrei Kvapil 868a7497d0 fix(ci): ensure correct latest release after backport publishing (#1800) ...

## 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
```

2026-01-09 14:54:01 +01:00

..

auto-release.yaml

fix(ci): remove GITHUB_TOKEN extraheader to trigger workflows

2026-01-09 14:54:00 +01:00

backport.yaml

[ci] Update korthout/backport-action@v3.2.1

2026-01-09 14:52:39 +01:00

pre-commit.yml

[mariadb] Add version management system with automated version updates

2025-12-02 00:36:00 +01:00

pull-requests-release.yaml

fix(ci): ensure correct latest release after backport publishing (#1800)

2026-01-09 14:54:01 +01:00

pull-requests.yaml

[core] Extract Talos package from installer (#1724)

2026-01-09 14:53:57 +01:00

retest.yaml

feat(ci): add /retest command to rerun tests from Prepare environment

2026-01-09 14:54:00 +01:00

tags.yaml

fix(ci): ensure correct latest release after backport publishing (#1800)

2026-01-09 14:54:01 +01:00

update-releasenotes.yaml

[workflow] Add GitHub Action to update release notes from changelogs (#1752)

2026-01-09 14:53:57 +01:00