actions / actions/runner

Runner version v2.330.0 is deprecated and cannot receive messages

Open
#4,305 2 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
6.3k
Forks
1.4k
Avg merge
1d 16h
Merged PRs (30d)
24

Description

Starting on March 16 2026, attempting to start a self-hosted runner built from the image ghcr.io/actions/actions-runner:2.330.0 fails to startup with the following errors

[RUNNER 2026-03-17 12:20:29Z ERR  Terminal] WRITE ERROR: An error occured: Runner version v2.330.0 is deprecated and cannot receive messages.
An error occured: Runner version v2.330.0 is deprecated and cannot receive messages.
[RUNNER 2026-03-17 12:20:29Z ERR  Listener] GitHub.DistributedTask.WebApi.AccessDeniedException: Runner version v2.330.0 is deprecated and cannot receive messages.
[RUNNER 2026-03-17 12:20:29Z ERR  Listener]    at GitHub.Actions.RunService.WebApi.BrokerHttpClient.GetRunnerMessageAsync(Nullable`1 sessionId, String runnerVersion, Nullable`1 status, String os, String architecture, Nullable`1 disableUpdate, CancellationToken cancellationToken)
[RUNNER 2026-03-17 12:20:29Z ERR  Listener]    at GitHub.Runner.Common.BrokerServer.<>c__DisplayClass7_0.<<GetRunnerMessageAsync>b__0>d.MoveNext()
[RUNNER 2026-03-17 12:20:29Z ERR  Listener] --- End of stack trace from previous location ---
[RUNNER 2026-03-17 12:20:29Z ERR  Listener]    at GitHub.Runner.Common.RunnerService.RetryRequest[T](Func`1 func, CancellationToken cancellationToken, Int32 maxAttempts, Func`2 shouldRetry)
[RUNNER 2026-03-17 12:20:29Z ERR  Listener]    at GitHub.Runner.Listener.BrokerMessageListener.GetNextMessageAsync(CancellationToken token)
[RUNNER 2026-03-17 12:20:29Z ERR  Listener]    at GitHub.Runner.Listener.Runner.RunAsync(RunnerSettings settings, Boolean runOnce)
[RUNNER 2026-03-17 12:20:29Z ERR  Listener]    at GitHub.Runner.Listener.Runner.RunAsync(RunnerSettings settings, Boolean runOnce)
[RUNNER 2026-03-17 12:20:29Z ERR  Listener]    at GitHub.Runner.Listener.Runner.RunAsync(RunnerSettings settings, Boolean runOnce)
[RUNNER 2026-03-17 12:20:29Z ERR  Listener]    at GitHub.Runner.Listener.Runner.ExecuteRunnerAsync(RunnerSettings settings, Boolean runOnce)
[RUNNER 2026-03-17 12:20:29Z ERR  Listener]    at GitHub.Runner.Listener.Runner.ExecuteCommand(CommandSettings command)
[RUNNER 2026-03-17 12:20:29Z ERR  Listener]    at GitHub.Runner.Listener.Program.MainAsync(IHostContext context, String[] args)
Runner listener exit with terminated error, stop the service, no retry needed.
Exiting runner...

Describe the bug
This is presumedly related to the announced minimum version enforcement (https://github.blog/changelog/2026-02-05-github-actions-self-hosted-runner-minimum-version-enforcement-extended/) but the blobpost there and subsequent blogposts all referencing it mention that the new minimum version is v2.329.0. v2.330.0 is also the last version that uses Ubuntu 22 so this means that Ubuntu 22 is also deprecated.

Is this intentional or has the wrong version been deprecated?

To Reproduce
Steps to reproduce the behavior:

  1. Create a self-hosted runner using ghcr.io/actions/actions-runner:2.330.0
  2. Observe that the runner fails to startup

Runner Version and Platform

2.330.0

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reported image ghcr.io/actions/actions-runner:2.330.0 and the BrokerMessageListener.GetNextMessageAsync stack-trace entry. Compare the observed rejection with the announced minimum-version enforcement and verify whether Ubuntu 22 support is affected. Done means confirming whether v2.330.0 was intentionally deprecated or identifying a version-enforcement error.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, github-actions
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.