The first half of 2026 reset two things at once for engineering teams: what continuous integration costs, and what it takes to keep delivery stable while AI pushes more change through your pipelines than ever.
Those two stories are connected, and the connection is the part worth your time.
The pricing reset On January 1, 2026, GitHub reduced prices for GitHub-hosted runners by up to 39%, with the size of the cut depending on the machine type (GitHub Changelog).
Standard hosted-runner usage on public repositories stays free, as it was before.
The DevOps publication SamExpert documented the specific per-minute moves.
A Linux 2-core runner dropped about 25% (from $0.008 to $0.006 per minute).
A Windows 2-core runner dropped about 38% (from $0.016 to $0.010).
A Linux 64-core arm64 runner dropped about 39% (from $0.160 to $0.098) (SamExpert).
If your CI runs mostly on hosted runners, that is real money back, and it is worth recalculating your monthly estimate against the new rates rather than assuming last year's numbers still hold.
The same December 2025 announcement carried a more controversial proposal: a $0.002 per-minute charge for self-hosted runner usage in private repositories, scheduled to start March 1, 2026 (DevClass).
GitHub framed it as ending a cross-subsidy, where revenue from hosted runners was effectively underwriting the cost of operating Actions for everyone, and said the large majority of customers would see no change to their bill.
The reaction from developers who run CI on their own hardware was sharp, with some publishing the monthly figures they expected to owe for compute they already pay to operate themselves.
Within about a week, GitHub posted that it was postponing the self-hosted billing change to re-evaluate its approach (SamExpert).
Postponed, it is worth being precise here, is not the same as withdrawn.
There is no new date and no guarantee the charge returns in its original form, but there is also no statement that it is gone for good.
If you operate self-hosted runners, this is a line item to keep watching rather than one you can cross off.
The takeaway is not "CI is cheap now, problem solved." Cheaper minutes lower the floor on per-minute cost.
They do nothing for the minutes you lose to flaky failures, cold starts, and re-runs, or for the engineering hours spent staring at a log to find out a job died because a disk filled up.
Price per minute is one variable.
Minutes wasted is the other, and it is usually the larger one.
That is where the second story comes in.
The reliability paradox Google's 2025 DORA report, drawn from survey responses from nearly 5,000 technology professionals around the world, found that 90% of respondents now use AI at work and more than 80% believe it has increased their productivity (Google Cloud).
That is genuinely good news.
This year DORA observed a positive relationship between AI adoption and both software delivery throughput and product performance, a reversal from the prior year, when the throughput signal was less encouraging.
The catch is stability.
The report states plainly that AI adoption "does continue to have a negative relationship with software delivery stability." The explanation is intuitive once you say it out loud: AI accelerates how fast code gets written, and that acceleration exposes weaknesses downstream.
Without robust control systems, an increase in change volume leads to instability (Google Cloud).
More pull requests, more merges, more pipeline runs, all arriving faster than the systems meant to catch problems were designed for.
There is a trust dimension too.
The same report found that about 30% of respondents report little or no trust in the code generated by AI, a slightly lower share than the year before but still a meaningful minority (Google Cloud).
People are shipping more AI-assisted code than they fully trust, which puts even more weight on the automated checks downstream.
DORA's broader framing is that AI is an amplifier.
As the repor