arch-upgrade-deps

Upgrades all repository dependencies to latest stable or LTS releases and validates with project gates.

89|10|Updated Sep 15, 2026
One-click install
npx skills add https://github.com/baristaze/swe_guidelines --skill arch-upgrade-deps-baristaze
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arch-upgrade-deps
Source: https://github.com/baristaze/swe_guidelines/tree/main/skills/arch-upgrade-deps
Command: npx skills add https://github.com/baristaze/swe_guidelines --skill arch-upgrade-deps-baristaze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Projects drift behind on dependency versions because releases keep coming and nobody moves them. This Skill upgrades every declared dependency—runtimes, tools, Docker images, CI actions, Terraform providers, and libraries—to its latest stable or active LTS release in one change, then proves the change with the repository's own gates. ## Core Features & Use Cases - Full dependency inventory: Scans .python-version, pyproject.toml, .nvmrc, package.json, Dockerfiles, compose files, CI workflows, and Terraform roots to build one plan table of every declaration. - Source-verified targets: Resolves each target from live maintainer release data (nodejs.org release index, endoflife.date, pnpm view), never from memory, and holds back releases with no patch behind them. - Gated validation with rollback: Runs make check, make infra-up, make migrate, and integration tests after editing, reverting any row that breaks a gate and reporting it as held back. - Use Case: Run it monthly on a service repository to move Node, Postgres, Valkey, Terraform providers, and all Python/npm libraries to current LTS lines, leaving an uncommitted diff and a report for a person to review. ## Quick Start Ask the assistant to upgrade every dependency in this repository to its latest stable or LTS release and run the gates, optionally limiting scope with names like python node postgres or previewing with --plan.

Frequently Asked Questions about arch-upgrade-deps

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade all dependencies in a repository at once?▼

Run the skill with no arguments to inventory every declared version, resolve targets from live release sources, edit each declaration, and validate with make check and integration tests. Use --plan to preview the upgrade table without editing anything.

How to upgrade only specific dependencies like Python or Node?▼

Pass dependency names as arguments, such as python node postgres, to limit the upgrade to those rows. All other dependencies remain unchanged, and the plan table and report cover only the named ones.

Does it upgrade a deployed database to a new major version?▼

No. A deployed database engine keeps its major version; only minors within that major move, in Terraform and the local compose image alike. A major upgrade is treated as a planned change with its own snapshot and rehearsal, never part of a dependency bump.

What happens when an upgrade breaks the build or tests?▼

The skill finds the row causing the failure, applies mechanical fixes named in the release's upgrade notes when possible, and otherwise reverts that row's edits with git restore. The row is reported as held back with the failing check, and validation reruns until everything else passes.

Why is a brand-new release not adopted immediately?▼

A release is adopted only once a patch release sits behind it, never the day it ships. When the newest release is a .0 or a patch published today, the target is the release before it, and the plan table notes this in its Line column.

Can it reset local data volumes when a backing service moves a major?▼

Only with the --reset-local-data flag, which lets validation run make infra-reset to recreate local dependency volumes. Without it, rows that move a major for a local backing service are held back whole so developer data is never removed.