Vercel ships one-click purge for poisoned build caches

Vercel added a one-click way to purge a team's entire Remote Cache of build and CI artifacts, per its changelog.

The button lives in Build and Deployment settings and wipes every cached artifact across the whole team at once, not per project. Vercel's changelog names the reason plainly: "when you believe poisoned artifacts are in your cache." That's language built for incident response, not routine cache cleanup.

Nothing in the changelog describes how a team would detect a poisoned artifact in the first place. There's no mention of alerting or scanning, only the purge itself. Whoever holds Team Owner access is left to make that call and act on it.

Wiping the whole team's cache also means every project sharing it loses its build speedup at the same time, the tradeoff for a lever built for emergencies rather than routine use.

Putting the poisoning language directly in a changelog entry, instead of a separate security bulletin, means teams find out about the risk from a routine release note. Find the button before a CI run is already serving bad artifacts, not after.