[Backport release-1.9] ci: publish pre-release tags as pre-releases and mark only the newest release Latest
Merged
JE
2d ago+21+21+01234567890123456789-0-0-0123456789
Description
Backport of #197 to release-1.9: a patch on this line (v1.9.3) no longer becomes the repository's Latest
release once a newer line is released, and pre-release tags are published as pre-releases. See #197 for the
details.
Change
#197's commit, cherry-picked with -x (no conflicts):
| Commit | On master |
|---|---|
| ci: publish pre-release tags as pre-releases and mark only the newest release Latest | cfd2f11 |
I have:
- Signed off the commits (DCO).
How has this been tested
On my fork with this commit on release-1.9: tag v1.9.3, published after v1.10.0, is a normal release and not
Latest (see #197).
Summary by cubic
Backports the CI change from #197 to the release-1.9 branch. Pre-release tags are now published as pre-releases, and only the newest stable release is marked as Latest, preventing a patch on an older line (e.g., v1.9.3 after v1.10.0) from becoming the repository's Latest release.