Texas just told data centers to prove they won't break the grid
Issue #008 · 4 min read
Texas just told data centers to prove they won't break the grid
Plus AI models trying to slip malware into open source, and what's actually new from GitHub and Vercel this week
The big story
Texas built its whole pitch around being the easy place to plug in a data center.
Loose rules, cheap land, a grid operator that said yes fast. That pitch just ended.
The state is now requiring data centers to pass an audit before they can connect to the power grid at all, according to The Verge. A separate report has the governor going further and pausing new grid connections outright while demand outstrips supply — TechCrunch has that story, and the same governor spent the last two years calling Texas the AI "epicenter," which is the detail that makes this sting — Ars Technica has the framing.
Here's why this isn't a Texas-only story. Every AI company's growth plan has a line item that says "and then we build more data centers," usually in whichever state makes that fastest. Texas was that state. If the easiest state to build in just added an audit gate, the assumption that compute capacity scales as fast as demand needs a second look.
If your roadmap has a dependency on inference getting cheaper or more available next year, this is the kind of thing that quietly pushes that date out — not because the AI got worse, but because the power to run it got harder to plug in.
What shipped
Anthropic's Claude Security plugin now covers the whole path from commit to production, not just the code review moment, through a new integration with GitLab. The pitch, in GitLab's own words, is that "agentic coding is moving faster than many enterprise governance programs can keep up with" — coding assistants can flag and fix vulnerabilities as code is written, but a commit still has to survive merges, dependencies, and everything after. Worth a look if your engineering org has coding agents shipping faster than your security review can keep pace with.
GitHub is retiring the Copilot Billing Preview app on August 4, folding spend visibility directly into GitHub billing settings — a small change, but if you've been pointing finance at that preview app for Copilot cost tracking, that link breaks now. Full note is in the GitHub changelog.
GitHub Spark is being shut down. As of August 4 it stops accepting new users and new apps, and existing users lose access entirely on August 31 — see the deprecation notice. If anyone on your team built something in Spark they actually rely on, this is the week to get it out.
What I'd actually do this week
- If your company runs infrastructure in Texas or is planning to, ask your infra lead directly whether the new audit requirement touches anything on your roadmap. Don't wait for it to surface in a capacity planning meeting three months from now.
- If you use Copilot billing tracking through the preview app, switch your finance dashboards over to GitHub billing settings before August 4 breaks the old link.
- Check whether anyone on your team has production dependencies built in GitHub Spark. You have until August 31 to get them out.
Reply and tell me what's actually breaking on your end this week — I read every one.