Inspecting the software and changes in GitHub Actions runners
You no longer have to guess which tools are available in the environment where your workflows run. This repository contains the source code for the virtual machine images used by GitHub Actions and Azure Pipelines. You can see at a glance which programs are installed on which operating systems and when they change.
Available images and label usage
Images based on Ubuntu, macOS, and Windows Server are provided for x64 and arm64 architectures. Using labels like ubuntu-latest in your workflow automatically selects the latest stable version of the image. You can use larger runners for macOS images by adding suffixes such as -xlarge or -large. When a -latest label moves to a new OS version, the transition is gradual with a sufficient notice period.
Installed software version policy
Popular tools are installed in multiple versions so that projects requiring specific versions can run immediately. Java includes all LTS versions, while Node.js includes the latest three LTS versions in parallel. Major tools like Docker, Python, and .NET Core also maintain multiple versions based on their respective latest version criteria. The selection of installed tools considers popularity, recency, licenses (MIT, Apache, GNU), and image size and time.
Release cycle and change tracking
Software in the runner images is typically updated weekly. When a release starts, a pre-release is created, and it becomes an official release upon completion. Subscribing to releases allows you to receive notifications about these changes. Breaking changes or image deprecations, which have significant impact, are announced in advance via the GitHub changelog and social media. You can find the exact software versions used in a specific build by checking the logs in the Set up job step.
Contribution methods and support scope
Bug reports and requests to add tools are accepted via issues. Opinions on image configuration or installed software can be discussed in discussions. However, for macOS images, although the source code is public, pull requests are not accepted because the CI for external contributions is still being prepared. To use other Linux distributions, you must use Docker or build a self-hosted runner yourself. This repository does not guarantee the performance of specific operating systems or tools; it focuses solely on defining what environment is provided.