Land a dependency update as one reviewed pull request. Read "Keeping dependencies current" in CONTRIBUTING.md for what a pin is and how the three pin files stay in step.
- Branch. Start from an up-to-date, clean
main, then createdeps/update-<YYYY-MM-DD>. Done whengit statusis clean on the new branch. - Survey. Run
vp run deps. Exit 0 means every pin is at its target: report that and stop. Otherwise read the table; a majorbumpor a deprecated pin is where a breaking change hides. - Update. Run
vp run deps update. It moves the pins, refreshes lockfiles, goldens, and snapshots, then runsvp run ready. When a step fails, the moved pins stay in the working tree: fix the cause at the abstraction that owns it (a template, an integration, a pin rule inpackages/integrations/src/deps), then runvp run deps updateagain. Done when it printsRepository checks passed. CI verifies every stack the pins reach on the pull request. - Check. Run
vp checkandvp run ready. Done when both pass on the final tree. - Commit. One commit,
chore(deps): update pinned dependencies, authored as the configured git user with noCo-authored-bytrailer. A tool that appends one gets bypassed withgit commit-tree. - Pull request. Push the branch and run
gh pr createagainstmain. The body lists each moved pin asname: old → newwith its bump, and names every breaking change you handled and where. Done when the pull request'scicheck passes; hand its URL to the user. A failingverifyjob names the stack and ends with its log; fix the cause as in step 3.