update-packages

Update Node.js and pnpm versions across package.json, .tool-versions, CI/CD workflows, and Dockerfiles.

1|Updated Nov 28, 2025

Search Tags:#automation #dependencies #pnpm #node.js #update #ci-cd #version-management

Ready to run

npx skills add https://github.com/yuann3/skills --skill update-packages

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-packages
Source: https://github.com/yuann3/skills/tree/main/.claude/skills/update-packages
Command: npx skills add https://github.com/yuann3/skills --skill update-packages

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures consistent, controlled upgrades of Node.js and pnpm across the entire codebase, preventing version drift and hotfix churn.

Core Features & Use Cases

Coordinate updates across multiple locations (package.json engines, .tool-versions, CI workflows, and Dockerfiles).
Verify against official sources and apply changes using npm-check-updates.
Safely test locally and in CI/CD after applying updates.

Quick Start

Run the update-packages workflow after the user explicitly requests updating Node.js or pnpm to refresh all references across the repository.

Frequently Asked Questions about update-packages

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

FAQPage Schema

How do I update Node.js and pnpm versions across an entire project?▼

Updating Node.js and pnpm across a project requires coordinating changes in package.json engines, .tool-versions, CI workflows, and Dockerfiles. This Skill automates safe, centralized updates across all these locations to prevent version drift and hotfix churn.

What's the best way to prevent version drift when upgrading Node.js in CI/CD configurations?▼

Preventing version drift during Node.js upgrades requires applying consistent versions across CI/CD configurations, Dockerfiles, and .tool-versions simultaneously. This Skill automates that centralized update process and verifies changes locally and in CI/CD after applying them.

Can I use npm-check-updates to update pnpm and Node.js in Dockerfiles and workflows?▼

Yes, npm-check-updates is used within this Skill's workflow to verify and apply version updates. It checks against official sources and updates references across Dockerfiles, CI/CD workflows, package.json engines, and .tool-versions.

How does centralized pnpm version management work for multi-location repositories?▼

Centralized pnpm version management works by scanning the repository for all version references and updating them in unison. This Skill targets package.json engines, .tool-versions, CI workflows, and Dockerfiles, then runs local verification to ensure consistency.

Why do my Node.js updates cause hotfix churn across different project files?▼

Node.js updates cause hotfix churn when version references are scattered across package.json, .tool-versions, CI workflows, and Dockerfiles without coordinated updates. This Skill resolves the issue by applying safe, centralized upgrades across all locations at once.

Do I need to manually verify Node.js version changes after updating package.json engines?▼

No, manual verification is handled automatically. After updating package.json engines and other locations, this Skill runs local verification and checks against official sources to ensure the Node.js and pnpm version changes are safe and consistent.