Batching Dependabot PRs

Why this exists

Dependabot opens one PR per update. Each one triggers a full CI run and, on platforms like Vercel or Netlify, a preview deployment. Ten open PRs means ten builds for changes that will all end up in the same lockfile anyway — and they serialize badly, because every merge invalidates the others' lockfiles and forces a rebase.

Collapsing them into a single branch turns N build cycles into one, and gives you a single place to verify the combined dependency graph — which is what actually ships. Bumps that pass in isolation can still conflict with each other; batching surfaces that before merge rather than after.

The shape of the work

Gather → apply manifest edits by hand → regenerate the lock → run every gate → drop only what's genuinely broken → one PR that documents what was held back.