One package per commit is slower to read and much faster when something breaks, because git bisect becomes a one-minute job. Step 6 matters: without the release notes the agent invents a migration path that never existed.
Workflow
Copied 4 times
1. `npm outdated`, then split the list: patch and minor in one branch, each major in its own.
2. Read the release notes yourself for anything major.
3. One package per commit: `npm i pkg@latest`, run the checks, commit.
4. After each install check `npm ls` for peer warnings and skim `git diff package-lock.json`.
5. Deploy the minor batch first and leave it a day before you start on the majors.
6. If a major needs code changes, paste the release notes into the prompt, not just the error.
AskVibe