This server release fixes three reliability issues affecting remote runs and CLI interactions.
- The runner cleanup process no longer deletes Linux runner pods that are actively executing a job. Previously, an internal bookkeeping edge case could force-remove a live pod mid-build, causing the GitHub job to report that the runner lost communication with the server. This guard now checks the pod’s runner container state before any removal.
- Completed job logs from GitHub Actions are now fetched reliably when GitHub responds with a redirect to a signed archive URL. The log worker follows the redirect manually and no longer forwards the GitHub installation token to the archive host, so completed run logs appear as expected instead of failing to ingest.
- The deprecation warning sent to older Tuist CLI clients now shows the correct CLI version number, such as
4.196.0, instead of mistakenly displaying a component release title likeRunners Controller 0.9.0. Update the CLI when prompted to keep server-side features working.