Runner version v2.321.0 is deprecated and cannot receive messages without prior notice

[cw-alexcroteau]

Describe the bug
We are suddenly running into "An error occured: Runner version v2.321.0 is deprecated and cannot receive messages.", suddenly.

To Reproduce
Steps to reproduce the behavior:

1. Create a runner with version v2.321.0

Expected behavior
Github should notify about deprecations or a least provide a calendar

Runner Version and Platform

Runner v2.321.0
Ubuntu 22.04

What's not working?

An error occured: Runner version v2.321.0 is deprecated and cannot receive messages.

[cw-alexcroteau]

As an update, this is an issue because of #3766, v2.323.0 seems to enforce NODE20_VERSION="20.19.0" in src/Misc/externals.sh. As mentioned in the other issue:

"""
For some users of cypress-io/github-action this is a breaking change due to Node.js' backport of require(esm) into Node.js 20.19.0.
"""

Is there a way to avoid that specific breaking change or work around it?

[k-walsh-gmg]

I am noticing the same issue regardless of the version specified(while using the latest v2.323.0 or v2.322.0)!

[emilio507]

I am noticing the same issue regardless of the version specified(while using the latest v2.323.0 or v2.322.0)!

If using the 2.323.0 you have to use runner controller and scale set helm chart version 0.10.1. I have issues with any other version.

[k-walsh-gmg]

I am noticing the same issue regardless of the version specified(while using the latest v2.323.0 or v2.322.0)!

If using the 2.323.0 you have to use runner controller and scale set helm chart version 0.10.1. I have issues with any other version.

Noticing regardless of the version used I receive this message in the logs. This was after explicitly setting to v2.323.0. Not sure if is directly related to your issue so created my own issue just in case!:
[RUNNER 2025-03-25 20:39:45Z ERR Terminal] WRITE ERROR: An error occured: Runner version v2.321.0 is deprecated and cannot receive messages.
An error occured: Runner version v2.321.0 is deprecated and cannot receive messages.

[kimxogus]

We already updated our runner v2.322.0, and having the same error and our self-hosted runners are failing too.

[yhrunykRW]

Facing the same issue

[oed-gruenerg]

@kimxogus We hit the same issue since yesterday. We've changed the image of the ephemeralrunnersets to version 2.323.0:

image: ghcr.io/actions/actions-runner:latest@sha256:831a2607a2618e4b79d9323b4c72330f3861768a061c2b92a845e9d214d80e5b

And right now the first pipeline runs looks good so far.

[agarner-dng]

I wonder if this is related, the timings are consistent at least, actions/runner-images#11101

[agulan]

We had the same issue at the same time. We have upgraded to use v2.323.0 and it has solved the issue for us.

[yhrunykRW]

+1, upgrade to v2.323.0 fix the issue

[Goodness73]

Describe the bug We are suddenly running into "An error occured: Runner version v2.321.0 is deprecated and cannot receive messages.", suddenly.

To Reproduce Steps to reproduce the behavior:

1. Create a runner with version v2.321.0

Expected behavior Github should notify about deprecations or a least provide a calendar

Runner Version and Platform

Runner v2.321.0 Ubuntu 22.04

What's not working?

An error occured: Runner version v2.321.0 is deprecated and cannot receive messages.

[nnaithamoud]

+1
Upgrade to v2.323.0 does fix the issue but was it a planned deprecation ? Mind you the runner version v2.321.0 was only a few months old so we didn't expect to have to bump the version that soon on our runners

[nocturne1]

GitHub has (poorly) documented that you have 30 days after a new release before it can be blocked.
https://github.blog/changelog/2022-02-01-github-actions-self-hosted-runners-can-now-disable-automatic-updates/

For compatibility with the GitHub Actions service, you will need to manually update your runner within 30 days of a new runner version being available

I've seen that they're pretty inconsistent on their timing, but this is the case. I hope it's better documented elsewhere, but that's what I've been aware of.