Four platforms changed a default this week. That's not unusual on its own — what makes this week worth a calendar entry is that three of the four are default-on and carry a July deadline, so doing nothing is itself a decision. Here's each one in what-happened / why-it-matters / what-to-do form, hardest deadline first.
1. npm v12 stops running install scripts — and it will break your CI#
What happened. npm v12, shipping this month, flips the biggest default in the JavaScript toolchain: preinstall, install, and postinstall lifecycle scripts from your dependencies no longer run unless you explicitly approve them. Even the implicit node-gyp rebuild that npm used to fire for any package with a binding.gyp is now blocked. Git dependencies and remote-URL (HTTPS tarball) dependencies also stop resolving unless you pass --allow-git and --allow-remote. GitHub's framing: install-time scripts are "the single largest code-execution surface in the npm ecosystem," and after a brutal year of supply-chain compromises, they're closing it.
Why it matters. This is the one on this list most likely to page you. The moment a developer or a CI runner upgrades to v12, any package that relied on a postinstall build — native modules, some ORMs, browser-driver tools like Playwright/Puppeteer — silently stops working until it's on your allowlist. It is a genuine security win and an urgent ops chore in the same release.
What to do. You can dress-rehearse today on npm 11.16.0+: run npm approve-scripts --allow-scripts-pending, review the exact packages v12 will block, approve the ones you trust, and commit the resulting allowlist in package.json. We wrote the full 15-minute migration — audit, approve, pin, and fix CI — as a companion how-to: npm v12 Broke Your Install: A 15-Minute Migration. This connects directly to why agent skills need supply-chain hygiene too: the attack surface is the code that runs when you fetch, not just when you ship.
2. Google Play opted your app into Catalog Access — opt out by July 22#
What happened. Google's new Play Catalog Access program lets registered third-party US Android app stores surface your Play listing — name, description, screenshots, metadata — inside their own storefronts. Developers were opted in by default, and the program goes live July 22. To keep your listing out of third-party stores, you have to actively opt out before then.
Why it matters. It's a distribution-and-branding change with a hard, near-term deadline that's very easy to miss in a console notification. It's also a downstream consequence of US app-store regulation — the walls are coming down whether or not you have an opinion about it.
What to do. Decide deliberately. Broader distribution is upside for some (more surfaces, more installs); for others it's brand dilution or a support-channel headache. Either way, make the call before July 22 rather than discovering the default. Check the Play Console notification and the Catalog Access help page.
3. MCP goes stateless — the spec locks July 28, and the SDKs break#
What happened. The next Model Context Protocol spec (the 2026-07-28 revision) makes the protocol core stateless: no Mcp-Session-Id, no initialize handshake, every request stands alone. Beta SDKs are already out — Python mcp v2, TypeScript v2, Go, and C# previews — and the Python and TypeScript ones ship as breaking major-version bumps.
Why it matters. Statelessness is a real scaling unlock: a remote MCP server can now sit behind an ordinary round-robin load balancer on plain HTTP, instead of needing sticky sessions. If you host or ship an MCP server for agents, that's cheaper horizontal scaling — but the SDK majors mean you have migration work to plan before the spec locks on July 28.
What to do. If you're building on MCP, pull the beta SDK for your language now and test against it, rather than waking up to a breaking bump the week it's final. New to the protocol? Start with what MCP actually is versus the alternatives, then read the SDK-beta announcement.
4. Cursor split its usage pools — re-forecast your AI-coding bill#
What happened. Effective July 1, Cursor restructured Teams pricing so every seat now has two separate included-usage pools: one for its first-party models (Auto, Composer) and one for third-party API models (Claude, GPT, Gemini). Standard stays $40/month with more first-party usage; a new Premium seat runs $120/month for roughly 5× the usage at 3× the price, aimed at heavy agent users.
Why it matters. This is the clearest signal yet of where AI-coding economics are heading: vendors ring-fencing their own cheaper models from expensive third-party API calls, and nudging power users up-tier. It changes how you forecast tooling spend and which model your team reaches for by default.
What to do. Look at your team's actual model mix. If your engineers lean on Claude/GPT through Cursor all day, the third-party pool is where you'll feel the pinch — and the tradeoffs across Cursor, Windsurf, Copilot, and Claude Code are worth a fresh look before the renewal lands.
The founder takeaway#
Three of these four are default-on with a July date attached. The security story of 2026 isn't a new exploit — it's platforms deciding that the safe default was worth breaking your build for.
Put two things on the calendar this week: opt out of Google Play Catalog Access by July 22 if you don't want it, and rehearse the npm v12 script approval before it lands in a red CI run. Then plan the MCP SDK bump ahead of July 28 and re-check your Cursor tier. None of these is hard on its own; all of them are easy to miss until they cost you a morning. For the deepest one, the npm migration walkthrough gets you from broken install to green in about fifteen minutes.
