dependency-upgrader

Guide auditable dependency upgrades across Gradle, Maven, and npm ecosystems with incremental updates and tests/builds.

130|15|Updated Dec 14, 2025

Search Tags:#Maven #Gradle #CI #version-bump #Node #migration-notes #dependency-upgrade

Ready to run

npx skills add https://github.com/jMerta/codex-skills --skill dependency-upgrader-jmerta

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dependency-upgrader
Source: https://github.com/jMerta/codex-skills/tree/main/dependency-upgrader
Command: npx skills add https://github.com/jMerta/codex-skills --skill dependency-upgrader-jmerta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the risky process of upgrading dependencies across Java/Kotlin and Node projects by providing a structured, auditable workflow that minimizes breaking changes.

Core Features & Use Cases

Detects project type and package managers (Gradle, Maven, npm, yarn, pnpm, bun).
Establishes a baseline of current versions from manifest and lockfiles.
Plans upgrades by selecting target versions using latest stable sources and migration notes.
Applies upgrades incrementally and runs tests/builds to catch breakages early.
Documents what changed and why, including notable migrations and follow-ups.

Quick Start

Example: upgrade Spring Boot to the latest compatible version across a multi-module Gradle project.

Frequently Asked Questions about dependency-upgrader

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

FAQPage Schema

How do I safely upgrade Maven and Gradle dependencies without breaking my Java project?▼

To safely upgrade Maven and Gradle dependencies, you need a structured workflow that detects toolchains, baselines current versions, applies updates incrementally, and runs tests to catch breakages early. This approach minimizes breaking changes across Java projects.

Can I upgrade a group of related dependencies like a Spring Boot family across multiple modules?▼

Yes, you can upgrade groups of related dependencies like a Spring Boot family across multi-module projects. The workflow coordinates group upgrades by selecting target versions using latest stable sources and migration notes to ensure compatibility across the entire ecosystem.

What is the best way to manage npm dependency updates and document migration notes?▼

The best way to manage npm dependency updates is using an auditable workflow that baselines current versions from lockfiles, applies updates incrementally, runs builds, and documents what changed and why, including notable migration notes and follow-up actions for Node projects.

Does this dependency upgrade workflow support package managers like yarn, pnpm, and bun?▼

Yes, the dependency upgrade workflow supports detecting and working with multiple Node package managers including npm, yarn, pnpm, and bun. It automatically detects the project type and package manager to establish an accurate baseline before planning changes.

Why should I upgrade dependencies incrementally rather than updating everything at once?▼

Upgrading dependencies incrementally is essential because it allows you to run tests and builds after each change, isolating breakages early. A full repo-wide update at once risks compounding breaking changes, making it difficult to identify which dependency caused a failure.

How do I plan dependency changes using latest stable sources and migration notes?▼

To plan dependency changes, the workflow selects target versions by checking latest stable sources and reviewing migration notes. This ensures you understand notable migrations and required follow-ups before applying any updates to your manifests or lockfiles.