Latest release (2.320.1) is broken

[pauldraper]

Your latest release at 2025-02-26 20:47 UTC is broken.

Feb 27 01:26:11 ip-10-83-28-92 run.sh[25455]: Current runner version: '2.320.1'
Feb 27 01:26:11 ip-10-83-28-92 run.sh[25455]: 2025-02-27 01:26:11Z: Listening for Jobs
Feb 27 01:26:12 ip-10-83-28-92 run.sh[25455]: An error occured: Runner version v2.320.1 is deprecated and cannot receive messages.

It seems you downgraded to v2.320.1 and immediately deprecated it?!?

I am using this script to find the latest version:

curl -LSs https://github.com/actions/runner/tags/ | grep -Eo " v[0-9]+.[0-9]+.[0-9]+" | head -n1 | tr -d 'v '

If should be doing something different to find the latest version, let me know.

[TingluoHuang]

2.320.1 is only for customers who still need on the deprecated OS that doesn't support dotnet 8 and node20.

[pauldraper]

I don't understand.

The latest release is supposed to not work?

I will pin, if you are releasing versions that don't work.

[Link-]

@pauldraper we do not advise using this approach to pulling the latest runner releases.

If you look at our workflows, we're excluding: --exclude-drafts --exclude-pre-releases when we fetch the latest.

https://github.com/actions/actions-runner-controller/blob/ddc872d3ee2ca2ca131eb2a86e14592ed6a1d332/.github/workflows/arc-update-runners-scheduled.yaml#L33

v2.320.1 is a backport release that's not intended for general consumption. It's a patch released for a limited set of customers who are still pinned to that version for technical reasons.

v2.320.1 is marked as a pre-release intentionally. Please update your script to pull the latest runner versions to exclude drafts and pre-releases.

We recommend that you use:

gh release list --repo actions/runner --exclude-drafts --exclude-pre-releases

[wherka-ama]

2.320.1 is only for customers who still need on the deprecated OS that doesn't support dotnet 8 and node20.

@TingluoHuang : I believe it was done in a bit careless manner. The impact was massive. I'm guessing not only on self-hosted side, we are mainly relying on but also on the github-hosted runners. Last night we had some jobs being stuck for many hours waiting for ubuntu-latest. Even if it was backport, which I understand the need for your gatekeeper should allow this version, which wasn't the case.

@Link- : I appreciate your suggestion, but it may be a bit confusing as you are citing the command which gives us the broken version. I think we don't have 100% bullet-proof way of getting that information. The closest one I could think of would be to use the gh cli instead of curl:

gh release list --repo actions/runner --exclude-drafts --exclude-pre-releases | head -n 1 | cut -f1

[Link-]

The impact was massive. I'm guessing not only on self-hosted side, we are mainly relying on but also on the github-hosted runners. Last night we had some jobs being stuck for many hours waiting for ubuntu-latest. Even if it was backport, which I understand the need for your gatekeeper should allow this version, which wasn't the case.

The 2.320.1 release does not affect GitHub hosted runners. If you saw impact yesterday, that was most likely due to another incident.

but it may be a bit confusing as you are citing the command which gives us the broken version.

@wherka-ama the output of the command I shared should be the following:

gh release list --repo actions/runner --exclude-drafts --exclude-pre-releases
TITLE     TYPE    TAG NAME  PUBLISHED
v2.322.0  Latest  v2.322.0  about 1 month ago
v2.321.0          v2.321.0  about 3 months ago
v2.320.0          v2.320.0  about 4 months ago
v2.319.1          v2.319.1  about 6 months ago
v2.319.0          v2.319.0  about 6 months ago
v2.317.0          v2.317.0  about 9 months ago
v2.316.1          v2.316.1  about 10 months ago
v2.316.0          v2.316.0  about 10 months ago
v2.315.0          v2.315.0  about 11 months ago
v2.314.1          v2.314.1  about 1 year ago
v2.314.0          v2.314.0  about 1 year ago
v2.313.0          v2.313.0  about 1 year ago
v2.312.0          v2.312.0  about 1 year ago
v2.311.0          v2.311.0  about 1 year ago
v2.310.2          v2.310.2  about 1 year ago
v2.310.1          v2.310.1  about 1 year ago
v2.310.0          v2.310.0  about 1 year ago
v2.309.0          v2.309.0  about 1 year ago
v2.308.0          v2.308.0  about 1 year ago
v2.307.1          v2.307.1  about 1 year ago
v2.307.0          v2.307.0  about 1 year ago
v2.306.0          v2.306.0  about 1 year ago
v2.305.0          v2.305.0  about 1 year ago
v2.304.0          v2.304.0  about 1 year ago
v2.303.0          v2.303.0  about 1 year ago
v2.302.1          v2.302.1  about 2 years ago
v2.302.0          v2.302.0  about 2 years ago
v2.285.3          v2.285.3  about 2 years ago
v2.299.2          v2.299.2  about 2 years ago
v2.296.3          v2.296.3  about 2 years ago

Are you seeing a different output?

[wherka-ama]

@Link- : the link you provided gives us the expected output indeed. The confusion comes from the fact you cited the command which should not be used. Some people are just too happy to copy it and try it asusming it's the correct one. Instead we could have an extract from the referenced doc where it is indeed doing what's expected.

Nevertheless, I really appreciate your guidance! Thanks a lot 👍

[lindluni]

The bullet-proof method for retrieving the "latest" release via the API, is using the Latest Release endpoint: https://docs.github.com/en/rest/releases/releases?apiVersion=2022-11-28#get-the-latest-release

[Link-]

@Link- : the link you provided gives us the expected output indeed. The confusion comes from the fact you cited the command which should not be used. Some people are just too happy to copy it and try it asusming it's the correct one. Instead we could have an extract from the referenced doc where it is indeed doing what's expected.

Nevertheless, I really appreciate your guidance! Thanks a lot 👍

AH! I see your point, command removed :)