pnpm-upgrade

Name: pnpm-upgrade
Availability: InStock
Author: pohlai88

Update pnpm versions across local and CI environments.

Updated Apr 5, 2026

Search Tags:#automation #workflow #tooling #pnpm #github-actions #ci #package-manager

Ready to run

npx skills add https://github.com/pohlai88/afenda-vite-react --skill pnpm-upgrade

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pnpm-upgrade
Source: https://github.com/pohlai88/afenda-vite-react/tree/main/.agents/skills/pnpm-upgrade
Command: npx skills add https://github.com/pohlai88/afenda-vite-react --skill pnpm-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps pnpm current across local and CI environments, ensuring consistency and repeatability.

Core Features & Use Cases

Refreshes the local pnpm version via pnpm self-update or corepack prepare
Aligns packageManager in package.json to the latest pnpm
Pins the latest pnpm/action-setup versions in .github/workflows to keep the CI toolchain in sync

Quick Start

Run pnpm self-update or corepack prepare pnpm@latest --activate, then update packageManager in package.json and pin the latest pnpm/action-setup in all workflows.

Frequently Asked Questions about pnpm-upgrade

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

FAQPage Schema

How do I update pnpm across my local environment and CI workflows?▼

To update pnpm across environments, run pnpm self-update or corepack prepare pnpm@latest --activate, then align the packageManager field in package.json and pin the latest pnpm/action-setup versions in your .github/workflows files.

What is the best way to keep pinned pnpm versions in GitHub Actions up to date?▼

Keeping pinned pnpm versions in GitHub Actions current requires updating the pnpm/action-setup version strings inside your .github/workflows files to match the latest release, ensuring your CI toolchain stays in sync with your local environment.

Do I need corepack to align the pnpm version in package.json?▼

You can use corepack prepare pnpm@latest --activate to refresh the local pnpm version, which then allows you to safely modify and align the packageManager field in your package.json to match that newly activated version.

Why does my CI pipeline use a different pnpm version than my local environment?▼

Your CI pipeline uses a different pnpm version because the pinned pnpm/action-setup in your GitHub Actions workflows is out of sync with the packageManager field defined in your local package.json file.

Can I automate pnpm toolchain refreshes for both local and CI environments?▼

You can automate the pnpm toolchain refresh by systematically running pnpm self-update, updating the packageManager pin in package.json, and modifying all CI workflow files to use the latest pnpm/action-setup version.