pnpm-upgrade

Update pnpm versions and pin pnpm/action-setup workflow references to latest release SHA.

Updated Aug 27, 2026

Search Tags:#automation #workflow #pnpm #update #github-actions #toolchain #ci

Ready to run

npx skills add https://github.com/redacharf/fin-punk --skill pnpm-upgrade-redacharf

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pnpm-upgrade
Source: https://github.com/redacharf/fin-punk/tree/main/.agents/skills/pnpm-upgrade
Command: npx skills add https://github.com/redacharf/fin-punk --skill pnpm-upgrade-redacharf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps the pnpm toolchain up-to-date across local development and CI pipelines.

Core Features & Use Cases

Update pnpm locally with pnpm self-update or corepack prepare pnpm@latest --activate.
Align packageManager in package.json to the latest PNPM version.
Refresh pinned pnpm/action-setup workflow references to the latest release commit SHA.

Quick Start

Run the pnpm-upgrade skill from the repository root to refresh the local pnpm version and update CI workflow pins.

Frequently Asked Questions about pnpm-upgrade

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

FAQPage Schema

How do I update the pnpm version in package.json and CI workflows?▼

To update the pnpm version, you can run pnpm self-update or corepack prepare pnpm@latest --activate, align the packageManager field in package.json, and refresh pinned pnpm/action-setup workflow references to the latest release commit SHA.

What's the best way to pin pnpm/action-setup to a specific release SHA in GitHub Actions?▼

Pinning pnpm/action-setup involves fetching the latest pnpm release tag, resolving its commit SHA, and updating your GitHub Actions workflow files with that exact SHA to keep CI pipelines fresh and secure.

How does keeping pnpm current across local development and CI pipelines work?▼

Keeping pnpm current works by applying a repeatable, script-driven process that updates the local pnpm toolchain, aligns packageManager in package.json, and pins pnpm/action-setup workflow references to the latest release SHA.

Do I need to manually resolve the commit SHA when updating pnpm in GitHub Actions?▼

No, you do not need to manually resolve the commit SHA. The pnpm-upgrade process automatically fetches the latest release tag and resolves the commit SHA to update workflow files with exact pins.

Can I use corepack to activate the latest pnpm version locally?▼

Yes, you can use corepack prepare pnpm@latest --activate to update the local pnpm version, ensuring your local development environment aligns with the latest pnpm release.

Why should I pin pnpm action-setup workflow references to an exact SHA?▼

Pinning pnpm action-setup workflow references to an exact SHA ensures your CI pipelines use a specific, verified release, preventing unexpected breaking changes from latest tag updates and keeping CI pins fresh.