Changelog
What changed that you can see and use, newest first. Only things that are live — nothing announced ahead of shipping. Follow it by RSS.
October 2026
A redesigned website, and a migration page
The public site has a new look. A new page walks through moving to our runners: the one-line change to your workflow file, and the pull request we can open for you.
Account credit on the Usage page
Any account credit on your organisation is shown on the Usage page with what is left of it. Credit is drawn down before your card on each invoice.
Settings, split into focused pages
Team, Billing, Integrations, Runners, Notifications and Security each have a page of their own, so every setting is where its name says it is.
Docker layer cache: unused layers expire after seven days
A cached layer that goes seven days without being used is removed on a schedule, so the cache holds what your builds actually reuse.
Sticky disks: every job gets its own copy
Concurrent jobs on the same repository each work on their own clone of the sticky disk, so they no longer wait for one another. When they save, the last one to finish wins.
Sticky-disk resets in the history
Every reset of a sticky disk now appears as its own entry in the disk's history, with who asked for it.
Told when a sticky disk is not saved
If a job would save something that looks like a credential onto a sticky disk, we refuse to save it and tell your organisation's notification channels, once per repository.
Protected sticky disks
Mark a repository's sticky disk as protected and only trusted runs of its default branch are given it; every other build gets an empty disk that is thrown away when the job ends.
Two-factor authentication
Protect your account with an authenticator app and recovery codes, and require two-factor sign-in for everyone in your organisation.
A public status page
See whether something is wrong on our side without signing in, with an incident log we post to.
Slack and Microsoft Teams notifications
Send notifications to a Slack or a Microsoft Teams channel, alongside email and webhooks.
Spend alerts and a monthly spend cap
Set up to ten spend alerts, and a hard monthly cap: once the month's spend reaches it, new Runners jobs are paused until you raise it or the month turns, and running jobs finish. The spend it checks is updated daily, so a month can run a little past it.
Usage trends, concurrency and CSV export
The Usage page charts how many jobs ran at once and how spend and minutes moved month by month, and exports usage and cost as CSV.
An activity feed
See who did what in your organisation: membership changes, billing and settings changes, and actions on jobs.
Cancel a job from its page
A running job can be cancelled from its own page by anyone whose role may act on runs.
A setup guide in the dashboard
New organisations get a step-by-step guide: the runs-on line to use, a setup checklist, and a reference for every runner size.
16-vCPU runners
The 16-vCPU runner size is available, at the price on the pricing page.
September 2026
Ask for sticky disks from Settings
Request sticky disks for your organisation from the Runners settings page; a person on our side switches them on.
Job pages that keep up
A job page left open on a running build follows it live, log and all.
Test results on your pull requests
Turn on test-result comments in Settings and a job's test results are posted to its pull request.
A pull request that moves a repository over
From the Repositories page, open a pull request that switches a repository's workflows onto our runners, and see any job it chose not to change and why.
The Repositories page
See every repository the app can reach and what state each is in, including whether its workflows have been moved onto our runners yet.
Terms of service and a privacy policy
Both are published, as drafts while the company details are finalised, and say so at the top.
Stronger passwords
Sign-up and password reset state the password rule up front and refuse passwords that appear in known breaches.
Documentation
A documentation site: getting started, runners, caching, administration, billing and an API reference.
The cache explorer
See what is in each repository's Actions cache, and its hit rate, from the Cache page.
August 2026
A pricing page read from the rates that bill you
Every price on the pricing page is read from the same rate card your invoice is built from.