Skip to content

Home / Blog / Cost and billing

GitHub Actions pricing changes: a dated log since January 2025

Every change GitHub has announced to Actions rates, included usage, billed items and limits since January 2025, each dated and linked to GitHub's announcement.

This post logs the 21 changes GitHub has announced since 1 January 2025 to what Actions costs and allows. Two of them are about the price of a minute: a cut of up to 39 per cent to hosted-runner rates that took effect on 1 January 2026, and a $0.002 per minute charge on self-hosted runners that GitHub announced on 16 December 2025 and postponed on 19 December 2025. Each entry is dated and linked to the GitHub page it was read from.

In short
  • GitHub cut hosted-runner prices by up to 39 per cent on 1 January 2026, and a standard 2-core Linux minute is now $0.006.
  • A $0.002 per minute self-hosted charge announced on 16 December 2025 was postponed on 19 December 2025.
  • From 20 November 2025 a repository's cache may exceed 10 GB, and the excess is billed storage.
  • Copilot code review has drawn on Actions minutes in private repositories since 1 June 2026.
  • None of the entries we read changes rounding each job up to a whole minute.

Each entry gives the day GitHub published it, what it changed and a link to GitHub’s own announcement, all read on 15 November 2026. Nothing here is our estimate of a change GitHub has not announced. The log is revised only when GitHub announces another change, and the date at the top of the post moves when it is.

How is this log kept, and what does it cover?

We read the title of every entry in GitHub’s changelog labelled Actions from 1 January 2025 to 13 November 2026, and the full text of each one that touches a rate, an included amount, something that is billed or a limit. The log lists those. It is a reading, and not a promise that GitHub announced nothing else, so a change that is missing is a reason to tell us and not evidence that none happened. Rows are newest first within each year.

None of the entries we read announces a change to rounding. GitHub’s runner pricing page still says that the minutes and partial minutes each job uses are rounded up to the nearest whole minute, so a 61-second job is billed as two. The rates in the log are the ones on that page; the pricing post explains them and the limits in one place are in the limits post.

What changed in 2026?

1 October 2026: retention covers checks, workflow runs and statuses. Checks, workflow runs and statuses are now governed by the same retention setting as artifacts and logs, with a default of 90 days, and are cleaned up when they pass it. GitHub’s announcement of 27 August 2026 says that artifacts and logs count toward billable Actions storage, so lowering the period can reduce storage cost and raising it can increase it, while checks, workflow run and status records are not billed for storage. The maximum for public repositories is 90 days (Actions retention now covers checks, runs, and statuses, and the announcement, read on 15 November 2026).

7 May 2026: concurrency groups allow larger queues. A concurrency group could hold one running and one pending run, and a newer run replaced the pending one. GitHub added queue: max, which allows up to 100 queued jobs or workflow runs per group (GitHub Actions concurrency groups now allow larger queues, read on 15 November 2026).

27 April 2026: Copilot code review consumes Actions minutes from 1 June 2026. GitHub announced that each Copilot code review on a private repository would consume Actions minutes from the plan’s included usage, with usage beyond that billed at standard Actions rates, for the Copilot Pro, Pro+, Business and Enterprise plans. Public repositories were not changed (GitHub Copilot code review will start consuming GitHub Actions minutes on June 1, 2026, read on 15 November 2026).

10 April 2026: a workflow run may be re-run 50 times. A re-run past 50, of the whole run or of some of its jobs, gets a failed check suite with an annotation. GitHub gave automations that tried hundreds of retries as the reason (Actions workflows are limited to 50 reruns, read on 15 November 2026).

3 March 2026: email at 90 and 100 per cent of included usage. GitHub began to email administrators and billing managers when included usage reaches 90 and 100 per cent of the month’s allowance, for Actions minutes and Actions storage among other metered products. It can be switched off on the Budgets and alerts page (Email notifications for included usage thresholds, read on 15 November 2026).

29 January 2026: arm64 standard runners in private repositories count toward included minutes. Linux and Windows arm64 standard runners, which had been for public repositories, became available in private ones with two vCPUs. GitHub says their usage counts toward the free minutes included in the plan (arm64 standard runners are now available in private repositories, read on 15 November 2026). GitHub’s rate page lists a Linux 2-core arm64 minute at $0.005.

22 January 2026: the 1 vCPU Linux runner is generally available. The runner, ubuntu-slim, has one vCPU and 5 GB of memory and limits a job to 15 minutes. It had been in public preview since 28 October 2025. GitHub’s rate page lists it at $0.002 a minute (1 vCPU Linux runner now generally available in GitHub Actions, read on 15 November 2026).

16 January 2026: a rate limit on cache uploads. GitHub set 200 cache uploads a minute per repository, saying that downloads are not affected, in response to repositories that uploaded many entries in very short periods. New uploads past the limit are rejected until it resets (Rate limiting for actions cache entries, read on 15 November 2026). The 429 post is about the error it produces.

1 January 2026: reduced hosted-runner pricing takes effect. GitHub reported price reductions of up to 39 per cent for GitHub-hosted runners, depending on the machine, and that standard runner usage in public repositories remains free. The 16 December 2025 announcement said the free usage quotas stay the same (Reduced pricing for GitHub-hosted runners usage, read on 15 November 2026).

What changed in 2025?

19 December 2025: the self-hosted charge is postponed. GitHub posted on its roadmap item for the charge that it was postponing the announced billing change for self-hosted Actions to re-evaluate its approach, and that the hosted-runner reduction would go ahead on 1 January 2026. GitHub’s billing page still lists self-hosted runners as free (GitHub Actions new pricing: self-hosted runner price increase, read on 15 November 2026).

16 December 2025: a price cut and a self-hosted charge are announced. GitHub announced that on 1 January 2026 it would cut hosted-runner prices by up to 39 per cent, and that on 1 March 2026 it would add a $0.002 per minute Actions cloud platform charge for self-hosted runners in private repositories, counting toward included minutes. The entry has since been updated with the postponement of the second change (Update to GitHub Actions pricing, read on 15 November 2026).

4 December 2025: 25 inputs on a workflow_dispatch workflow. The limit rose from 10 to 25 (Actions workflow dispatch workflows now support 25 inputs, read on 15 November 2026).

20 November 2025: cache above 10 GB is billed storage. A repository’s cache may now exceed 10 GB on a pay-as-you-go basis. Every repository keeps 10 GB at no charge, and an enterprise, organization or repository admin can raise the size limit and set a retention limit in days. Going beyond 10 GB needs a Pro, Team or Enterprise account, and a billing owner can set a budget on the new line, after which the cache becomes read-only until the next billing cycle (GitHub Actions cache size can now exceed 10 GB per repository, read on 15 November 2026). The cache limit post has the rest.

6 November 2025: higher limits on reusable workflows. A workflow run may use up to 10 nested reusable workflows and call up to 50 workflows in total, where the previous limits were four and 20 (New releases for GitHub Actions – November 2025, read on 15 November 2026).

28 October 2025: the 1 vCPU Linux runner enters public preview. It runs a job in a container, with one vCPU and 5 GB of memory, and limits it to 15 minutes (1 vCPU Linux runner now available in GitHub Actions in public preview, read on 15 November 2026).

29 September 2025: enforcement of a new cache eviction policy is delayed. GitHub said it was moving enforcement from mid-October to November. Then, each repository had a 10 GB cache maximum and the oldest entries were evicted every 24 hours; GitHub said it was changing the interval to every hour, which could mean more cache thrashing for repositories using more than 10 GB in a day (New date for enforcement of cache eviction policy, read on 15 November 2026).

7 August 2025: arm64 standard runners for public repositories are generally available. Linux and Windows arm64 standard runners with four vCPUs, free in public repositories (arm64 hosted runners for public repositories are now generally available, read on 15 November 2026).

14 April 2025: free Windows arm64 runners in public repositories, in preview. Windows arm64 hosted runners with four vCPUs and a Windows 11 image became free in public repositories (Windows arm64 hosted runners now available in public preview, read on 15 November 2026).

9 April 2025: a 96 vCPU larger runner. A new size with 96 vCPUs, 384 GB of memory and 2040 GiB of SSD, billed at the larger-runner rates on GitHub’s billing page, which now list Linux 96-core at $0.252 a minute (GitHub Actions hosted runner fleet now includes 96 vCPU larger runner, read on 15 November 2026).

2 February 2025: the workflow usage endpoints close. GitHub said that as Enterprise and Team plan customers moved to its new billing platform, which it expected to complete by 1 April 2025, the Get workflow usage and Get workflow run usage endpoints would close. Usage is available by SKU, organization and repository from the billing platform’s usage endpoint, and per workflow in the usage report (Actions Get workflow usage and Get workflow run usage endpoints closing down, read on 15 November 2026).

16 January 2025: free arm64 runners in public repositories, in preview. Linux arm64 hosted runners with four vCPUs became free in public repositories, and did not work in private ones (Linux arm64 hosted runners now available for free in public repositories, read on 15 November 2026).

What has not changed?

Three things in GitHub’s own documentation read as they did before the changes above. Standard GitHub-hosted runners in public repositories are free, and so are self-hosted runners; GitHub’s Actions billing page lists both as usage that does not draw from the included amount. And each job is still rounded up to a whole minute. A plan’s included compute is stated on GitHub’s current pages as a dollar amount a month: $12 on Free, $18 on Pro and Team and $300 on Enterprise Cloud. GitHub said on 16 December 2025 that the free usage minute quotas would remain the same.

What do these changes mean for a monthly bill?

The change that lowers a bill is the 1 January 2026 cut: a standard 2-core Linux minute is $0.006 on GitHub’s rate page today. How far a given month falls depends on how many minutes it has, so the cost calculator takes your own numbers, and our 10,000-minute and 50,000-minute pages work through two common sizes. The pricing page has our own rates, which are set per minute with no change to how a minute is counted.

Rounding is the same rule before and after every entry above. It adds the most to a month made of many short jobs, because each job is rounded up on its own. If a rule in this log changes your plans, the guide to choosing a runner provider has the questions to ask about it, and the post on running less has the changes that reduce the minutes you pay for in the first place.

Sources

Frequently asked questions

Did GitHub change Actions pricing in 2026?

Yes. Hosted-runner prices fell by up to 39 per cent, depending on the machine, from 1 January 2026, and standard runner usage in public repositories stayed free. GitHub also announced a $0.002 per minute self-hosted charge for 1 March 2026, then postponed it.

Are self-hosted runners still free in GitHub Actions?

Yes. GitHub announced a $0.002 per minute charge on 16 December 2025 and said on 19 December 2025 that it was postponing it. Its billing page still lists self-hosted runners as free usage that does not draw on included compute.

Does Copilot code review use GitHub Actions minutes?

Yes, from 1 June 2026, for reviews on private repositories under the Copilot Pro, Pro+, Business and Enterprise plans. The minutes come from the plan's included usage, and usage beyond it is billed at standard Actions rates. Public repositories are unchanged.

Did GitHub change how Actions minutes are rounded?

Not in any entry we read since January 2025. GitHub's runner pricing page still says the minutes and partial minutes each job uses are rounded up to the nearest whole minute, so a 61-second job is billed as two.

Move your CI onto our runners with one line

Connect GitHub

Card required. You pay only for the minutes your jobs run.

.github/workflows/ci.yml
jobs: test:- runs-on: ubuntu-latest+ runs-on: runnersio-4vcpu-ubuntu-2404 steps: - uses: actions/checkout@v4 - run: make test+ build:+ runs-on: runnersio-32vcpu-ubuntu-2404