3 ms·
from the tweet [1]: "We’ve read your posts and heard your feedback. 1. We’re postponing the announced billing change for self-hosted GitHub Actions to take ti
by techterrier 10mo ago
from the tweet [1]:
"We’ve read your posts and heard your feedback.
1. We’re postponing the announced billing change for self-hosted GitHub Actions to take time to re-evaluate our approach.
2. We are continuing to reduce hosted-runners prices by up to 39% on January 1, 2026.
We have real costs"
^ theres more in the actual tweet, but the preview that gets unfurled on discord cuts off there. That last lines a killer, poor olde microsoft
1. https://x.com/i/status/2001372894882918548 https://x.com/i/status/2001372894882918548
- bilekas 10mo ago> We have real costs" Am i wrong or didn't they have a bug in the action runners that would basically cycle the CPU infinitely ? > https://github.com/actions/runner/issues/2380 https://github.com/actions/runner/issues/2380 > https://github.com/actions/runner/issues/3792 https://github.com/actions/runner/issues/3792 Didn't they take years to fix this ? Or its unrelated ?
- Narretz 10mo agoThey are talking about the cost to run the Actions control plane and the scheduler that is not executed on the runner itself.
- codeflo 10mo agoThey have all kinds of costs hosting GitHub, which is why there's per seat pricing for companies. If those prices are too low, they can always increase them. Charging on top of that per minute of using your own infrastructure felt greedy to me. And the fact that this was supposed to be tied to one of the lesser-maintained features of GitHub raised eyebrows on top of that.