When bumping all packages to the same version sequentially, npm v7+
rejects the intermediate state where common@<new> doesn't satisfy
im's peerDep >=0.2.0. All packages are published together so the
constraint is always satisfied in the final released state.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>