I updated a Gitea instance from 1.22.1 to 1.23.6 yesterday. Since the update my runner went missing. Debugging this I found out that it (FWIW, the runner is at version 0.2.11) fails calling the Gitea API which now returns 405:
Mar 31 21:01:47 host gitea_runner[655]: time="2025-03-31T19:01:47Z" level=info msg="Starting runner daemon"
Mar 31 21:01:47 host gitea_runner[655]: time="2025-03-31T19:01:47Z" level=error msg="fail to invoke Declare" error="unknown: 405 Method Not Allowed"
Mar 31 21:01:47 host gitea_runner[655]: Error: unknown: 405 Method Not Allowed
From the logs of the proxy in front of my Gitea, I can see that the path that is being requested (using GET) is: /api/actions/runner.v1.RunnerService/Declare
Trying to find out why this happens, I had a look at git.mydomain.com/api/swagger where I cannot find a actions resource at all.
Did I miss a required configuration change in my upgrade that is required to expose this portion of the API? Is this a version mismatch between my Gitea instance and the runner? Is this a bug?