SuperAPI AI Directory

update-deps

General & other

View repository

Updated 10-16 06:44

About this skill

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.

  1. Branch. Start from an up-to-date, clean main, then create deps/update-<YYYY-MM-DD>. Done when git status is clean on the new branch.
  2. Survey. Run vp run deps. Exit 0 means every pin is at its target: report that and stop. Otherwise read the table; a major bump or a deprecated pin is where a breaking change hides.
  3. Update. Run vp run deps update. It moves the pins, refreshes lockfiles, goldens, and snapshots, then runs vp 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 in packages/integrations/src/deps), then run vp run deps update again. Done when it prints Repository checks passed. CI verifies every stack the pins reach on the pull request.
  4. Check. Run vp check and vp run ready. Done when both pass on the final tree.
  5. Commit. One commit, chore(deps): update pinned dependencies, authored as the configured git user with no Co-authored-by trailer. A tool that appends one gets bypassed with git commit-tree.
  6. Pull request. Push the branch and run gh pr create against main. The body lists each moved pin as name: old → new with its bump, and names every breaking change you handled and where. Done when the pull request's ci check passes; hand its URL to the user. A failing verify job names the stack and ends with its log; fix the cause as in step 3.