dependency-upgrade
/dependency-upgrade
Upgrade dependencies safely using pnpm catalog, checking for breaking changes, and testing upgrades. Use when updating packages, applying security patches, upgrading major versions, resolving dependency conflicts, or modernizing tech stack.
- Author
- motormetrics ↗
- Repository
- motormetrics ↗
- Licence
- MIT
- Last repository change
- 28.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Upgrade dependencies safely using pnpm catalog, checking for breaking changes, and testing upgrades. Use when updating packages, applying security patches, upgrading major versions, resolving dependency conflicts, or modernizing tech stack.
Original author description
Upgrade dependencies safely using pnpm catalog, checking for breaking changes, and testing upgrades. Use when updating packages, applying security patches, upgrading major versions, resolving dependency conflicts, or modernizing tech stack.
How it works
- Check for Updates
- Upgrade Process
- Major Version Upgrades
- Security Updates
- Dependency Conflicts
- Rollback
- Troubleshooting
- Best Practices
- References
SKILL.md preview
---
name: dependency-upgrade
description: Upgrade dependencies safely using pnpm catalog, checking for breaking changes, and testing upgrades. Use when updating packages, applying security patches, upgrading major versions, resolving dependency conflicts, or modernizing tech stack.
allowed-tools: Read, Edit, Write, Bash, Grep, Glob
---
# Dependency Upgrade Skill
Uses **pnpm with catalog** for centralized dependency management.
## Check for Updates
```bash
pnpm outdated # Check all outdated
pnpm -r outdated # Across workspace
pnpm -F /api outdated # Specific package
pnpm dlx taze --interactive # Interactive upgrade
```
## Upgrade Process
### 1. Update Catalog
```yaml
# pnpm-workspace.yaml
catalog:
next: ^16.0.0 # Upgraded from ^15.0.0
react: ^19.0.0
```
Packages reference with `"package": "catalog:"` in package.json.
### 2. Install and Test
```bash
pnpm install
pnpm tsc --noEmit # Type check
pnpm test # Unit tests
pnpm biome check . # Lint
pnpm build # Build
pnpm dev # Manual testing
```
### 3. Fix Breaking Changes
```typescript
// Example: Next.js 16 async params
// Before
export default function Page({ params }: { params: { id: string } }) {
return <div>{params.id}</div>;
}
// After
export default async function Page({ params }: { params: Promise<{ id: string }> }) {
const { id } = await params;
return <div>{id}</div>;
}
```
### 4. Commit
```bash
git commit -m "chore(deps): upgrade Next.js to v16
- Upgrade Next.js 15 → 16
- Upgrade React 18 → 19
- Fix async params migration
BREAKING CHANGE: Requires Node.js 20+"
```
## Major Version Upgrades
### Next.js
```bash
pnpm dlx @next/codemod@latest upgrade latest # Run codemod
# Update catalog: next: ^16.0.0, react: ^19.0.0
pnpm install
# Fix: async params, async cookies/headers
```
### TypeScript
```bash
# Update catalog: typescript: ^5.3.3
pnpm install
pnpm tsc --noEmit # Fix type errors
```
### Drizzle ORM
```bash
# Update catalog: drizzle-orm: ^0.30.0, drizzle-kit: ^0.20.0
pnpm install
pnpm -F /database db:generate # If schema changed
```
## Security Updates
```bash
pnpm audit # Check vulnerabilities
pnpm audit --fix # Auto-fix
# Or manually update vulnerable package in catalog
```
## Dependency Conflicts
```bash
pnpm why package-name # Check dependency chain
pnpm dedupe # Deduplicate
```
Use overrides as last resort:
```json
{ "pnpm": { "overrides": { "react": "^19.0.0" } } }
```
## Rollback
```bash
git reset --hard HEAD
# Or revert lockfile:
git checkout main -- pnpm-lock.yaml
pnpm install
```
## Troubleshooting
```bash
# Lockfile conflicts
rm pnpm-lock.yaml && pnpm install
# Build failures after upgrade
rm -rf node_modules .turbo dist .next && pnpm install && pnpm build
```
## Best Practices
1. **Use Catalog**: Centralize versions in pnpm-workspace.yaml
2. **Test Thoroughly**: Run all tests after upgrades
3. **Read Changelogs**: Review breaking changes before upgrading
4. **Upgrade Incrementally**: Don't update everything at once
5. **Commit Separately**: Separate dependency upgrades from features
6. **Automate Security**: Use Dependabot for security patches
## References
- pnpm Catalog: https://pnpm.io/catalogs
- Next.js Codemods: https://nextjs.org/docs/app/building-your-application/upgrading/codemods
- See `security` skill for vulnerability scanning
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · motormetrics/motormetrics | 100 | MIT |
| event4u-app/agent-config | 100 | MIT |
| rpraharaj/forward-deployed-engineer | 100 | MIT |
| rootcastleco/rei-skills | 100 | MIT |
| motormetrics/motormetrics | 100 | MIT |
| Kuan-AI-com/agent-skills | 100 | MIT |
| itsofficialadi/boundiff | 100 | MIT |
| wshobson/agents | 100 | MIT |
| rmyndharis/antigravity-skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version f158f2720109 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100dependency-update
Dependabot-style dependency maintenance for any pnpm workspace: update packages (pnpm catalog or package.json) to safe versions and flag breaking or stale-major upgrades; bump Node/pnpm versions; review a Dependabot PR and post a verdict comment. Use when asked to update or… - 90dependency-maintenance
Dependency maintenance. Use when adding, moving, or upgrading dependencies, changing pnpm or JavaScript runtimes, updating TypeScript or build/test tools, or changing native-build policy, patches, or test images. - 85pnpm
Node.js package manager with strict dependency resolution. Use when running pnpm specific commands, configuring workspaces, or managing dependencies with catalogs, patches, or overrides. - 100bump-deps
Analyze and upgrade dependencies with breaking change detection. Use when updating frontend (pnpm) or backend (uv) dependencies. - 100package-upgrade
[Code Quality] Use when analyzing npm package upgrades, outdated dependencies or breaking changes and preparing a phased upgrade plan. - 100package-upgrade
[Code Quality] Use when analyzing npm package upgrades, outdated dependencies or breaking changes and preparing a phased upgrade plan.