The Self-hosted Runners section of the CircleCI web app showed the self-hosted runner’s hostname instead of the self-hosted runner’s name. This has been fixed to show the name.

Runner Release 3.0.25

Both Machine and Container Runner:

As previously reported https://circleci.com/changelog/launch-agent-1-x-variants-eol/.

Runner Release 3.0.24

Both Machine and Container Runner:

We will end support for all 1.x variants of runner launch agent on July 31st 2024. It has been replaced with Machine Runner 3.0. You can learn more about machine runner and migration here.

What’s New

• Add circleci symlink to the circleci-agent binary within tasks
• Retry loading resource class token secrets on retryable errors
• Update various dependencies

What’s New

• Upgrade to Go 1.20
• Migrate Helm chart to new image repository: https://hub.docker.com/r/circleci/runner-agent/
• Improve error handling and increase reliability in the task worker loop
• Sample low-value health check logs when using the informational logging level

What’s New

• Bugfixes and package updates

What’s New

• Add lifecycle pre-stop command to gracefully terminate task agent on shutdown
• Ensure all Task lifecycle step events can be sent, even on shutdown of the agent and the context is cancelled
• Don’t delete the task pod if task agent is still running
  • This is related to issue https://github.com/kubernetes/client-go/issues/724. The remotecommand package may not always handle network disconnects on the exec command, returning a nil error. Therefore, we don’t delete the task pod in this case, giving a chance for the task to complete in an “orphaned” state.
• Prevent Task lifecycle step output from being lost during long-running jobs
• Improve task cleanup liveness check robustness and add extra logging
• Fix draining and cleanup of a task on shutdown of the runner agent
• Use stricter task pod config parsing with more helpful error messaging

What’s New

• Various dependency updates
• Fix for task liveness probe retries not being respected
• Fix for task pods not being cleaned up when exiting with a run error

What’s New

• Fix Kubernetes cleanup panic when pod allocation fails
• Fix incorrect liveness probe failures if the task agent PID file is deleted
• Log platform info to the Task lifecycle step
• Make user agent header driver specific

What’s New

• Log errors from calls to Kubernetes API when loading token secrets on Kubernetes driver startup
• Set reasonable resource requests and limits for logging containers
• Add a liveness probe to check the health of the task-agent process
• Respect node RBAC permission setting in K8s GC
• Fix for custom Docker registry names
• Fix for broken pipes while copying task agent when using Alpine-based images on MicroK8s
• Fix for the task token from being able to be exposed in a job
• Support Bash parameter expansion syntax in the job config file
• Improve logging container configuration:
  • Only mount the service account token if there are service containers and therefore a logging container
  • Make the logging container respect the image pull policy of the task pod config, if set. This matches the behaviour of the primary and secondary containers in the task pod.
• Improve task pod event logging in the Task lifecycle step

What’s New

This release includes dependency updates and security patches.