dependency-upgrade

Safely upgrade dependencies by using pnpm's catalog to manage centralized versions across your workspace. Run pnpm outdated to identify packages needing updates, then use the interactive upgrade tool to apply changes. After upgrading, the workflow validates installations, runs tests, type-checks, lints, and builds to ensure compatibility before committing.

Use a catalog-based approach with pnpm to apply security patches uniformly across apps/* and packages/* directories. This centralizes version control and ensures all dependents receive the same patch version, eliminating version conflicts and inconsistencies in your monorepo.

Yes. The upgrade workflow reviews changelogs and migration guides before applying major version changes, then validates compatibility through testing and type-checking. This catches breaking changes early and ensures all workspace packages remain compatible after upgrades.

The pnpm catalog centralizes dependency versions, eliminating conflicts by design. When upgrading, the workflow installs, tests, and type-checks across the entire workspace to surface incompatibilities. Conflicts are resolved at the catalog level before propagating to dependent apps and packages.

No. The upgrade workflow automates validation by running install, tests, type-checks, linting, and builds automatically after each upgrade. You review the results and prepare the state for commit, but manual testing across packages is handled by the procedure.

Security patches fix vulnerabilities with no breaking changes; minor upgrades add backward-compatible features; major upgrades include breaking changes. The workflow guides you through each type, reviewing impact and migration steps, then validates all packages remain compatible before committing.