I’ve lived through five major technology shifts: mainframe to Windows in the early ‘90s, internet computing in the late ‘90s and early 2000s, Agile in the mid-2000s, cloud through the 2010s, and now AI. You learn things by surviving that many. You learn that vendors oversell. That leadership wants results yesterday. That the breathless predictions almost never land on the calendar that everyone promised. So you learn to discount the hype. And that reflex, the one thing that five shifts trained into me, is the thing I’d warn other veterans about right now. The hype curve lies in both directions. Everyone knows it inflates expectations early. What we forget is that it deflates them later, right around the time the technology actually starts to matter. The people who got burned chasing the last four shifts are the ones primed to under-react to this one. The engineer who lost a year to a premature cloud migration is the same engineer waving off agentic coding today. Same scar, wron...
GitHub is resuming enforcement of minimum version requirements for GitHub Actions self-hosted runners — and this time, the deadlines are firm. After a rocky start that included multiple delays and a temporary pause earlier this year, GitHub has published a clear enforcement timeline for both GitHub Enterprise Cloud and GitHub Enterprise Cloud with Data Residency. If your team runs self-hosted runners and hasn’t upgraded them yet, now is the time to act. Why This Is Happening In early 2024, the GitHub Actions team began rearchitecting the backend services that power job execution and runner communication. That foundational rebuild now handles over 120 million jobs per day — more than three times the pre-migration volume — and lets enterprises start seven times more jobs per minute than before. Version enforcement is the final step in completing that migration. Older runner versions that are incompatible with the updated infrastructure can no longer be supported as all runners m...