cozystack/.github
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
..
ISSUE_TEMPLATE Update .github/ISSUE_TEMPLATE/bug_report.md 2025-10-08 17:30:56 +03:00
workflows fix(ci): ensure correct latest release after backport publishing (#1800) 2026-01-09 14:54:01 +01:00
CODEOWNERS Update CODEOWNERS 2025-10-20 14:46:10 +03:00
PULL_REQUEST_TEMPLATE.md [maintenance] Add a PR template 2025-06-26 10:14:25 +03:00