Latest release when querying github is NOT newest version

[erstcloudbot]

What happened?

Asking github for the latest releases gives version 1.24.16 when 1.27.4 is available.

What did you expect to happen?

Get 1.27.4

How can we reproduce it (as minimally and precisely as possible)?

curl https://api.github.com/repos/kubernetes/kubernetes/releases/latest

Anything else we need to know?

No response

Kubernetes version

$ kubectl version
# paste output here

Cloud provider

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[saschagrunert]

/sig release

Right now it depends on the order we release the patches, so technically it is the latest release, but not logically.

We could fix that by running krel release for the latest release branch at the end of the process or by adding a technical solution. Thoughts on that @kubernetes/release-managers ?

[xmudrii]

We could fix that by running krel release for the latest release branch at the end of the process or by adding a technical solution.

GitHub supports marking a release as the latest. We need to check if we can do that automatically via krel

[xmudrii]

I'll be taking care of this
/assign

[xmudrii]

My colleague @embik would like to give this a try, I'm assigning this issue to him, but he's not an org member yet so this might fail
/assign @embik

[k8s-ci-robot]

@xmudrii: GitHub didn't allow me to assign the following users: embik.

Note that only kubernetes members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

My colleague @embik would like to give this a try, I'm assigning this issue to him, but he's not an org member yet so this might fail
/assign @embik

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[xmudrii]

A fix for this issue (kubernetes/release#3559) has been merged. However, we need a new krel release for this fix to be in effect, so I'll keep the issue open until then.

[xmudrii]

This should be fixed now, thanks a lot @embik for taking care of this!!
/close

[k8s-ci-robot]

@xmudrii: Closing this issue.

In response to this:

This should be fixed now, thanks a lot @embik for taking care of this!!
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.