dependency-updates

Automate coordinated dependency version updates across a pnpm monorepo.

23|3|Updated Jun 28, 2022
One-click install
npx skills add https://github.com/Esposter/Esposter --skill dependency-updates-esposter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-updates
Source: https://github.com/Esposter/Esposter/tree/main/.agents/skills/dependency-updates
Command: npx skills add https://github.com/Esposter/Esposter --skill dependency-updates-esposter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Esposter dependency update process centralizes and enforces consistency across all package versions tracked in pnpm-workspace.yaml, ensuring reliable upgrades and predictable lockfile states.

Core Features & Use Cases

  • Centralized version management across monorepos using catalog entries in pnpm-workspace.yaml
  • Enforces caret rules for non-pinned packages and clearly documents pinned packages and tracked issues
  • Guided workflow for outdated checks, version bumps, and lockfile refresh coordination

Quick Start

Update the catalog entries in pnpm-workspace.yaml and then run pnpm refresh:lockfile to apply changes and verify synchronization.

Frequently Asked Questions about dependency-updates

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

FAQPage Schema
How do I coordinate dependency updates across a pnpm monorepo?

To handle pinned packages during pnpm catalog updates, the process clearly documents pinned packages and tracked issues while enforcing caret rules for non-pinned packages. This ensures predictable lockfile states across the monorepo.

What is the best way to align package.json versions with pnpm-workspace.yaml?

Lockfile refresh guidance is prompted during the dependency update workflow rather than executed automatically. You manually run pnpm refresh:lockfile after updating pnpm-workspace.yaml to apply changes and verify version synchronization.

How does caret rule enforcement work for non-pinned packages in a pnpm workspace?

Caret rule enforcement for non-pinned packages in a pnpm workspace automatically applies semver caret constraints during version bumps. This allows minor version updates while preventing breaking changes from major version upgrades.

Can I use this to manage monorepo dependency updates without manually editing each package.json?

Yes, you can manage monorepo dependency updates without manual package.json edits by centralizing versions in pnpm-workspace.yaml catalog entries. The workflow coordinates version bumps and validates that all workspace references stay synchronized automatically.