pnpm-upgrade

Update pnpm, prepare Corepack, and align packageManager pins in GitHub Actions workflows.

3.6k|897|Updated May 31, 2025
One-click install
npx skills add https://github.com/openai/openai-agents-js --skill pnpm-upgrade-openai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pnpm-upgrade
Source: https://github.com/openai/openai-agents-js/tree/main/.agents/skills/pnpm-upgrade
Command: npx skills add https://github.com/openai/openai-agents-js --skill pnpm-upgrade-openai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps pnpm and CI pins in sync by updating pnpm locally, preparing Corepack, and aligning packageManager in package.json.

Core Features & Use Cases

  • Updates pnpm to the latest version and ensures Corepack is prepared for the new version.
  • Aligns packageManager in package.json and pins the pnpm versions used in GitHub Actions workflows.
  • Use case: refreshing the pnpm toolchain manually or as part of automated maintenance to ensure consistent toolchain across environments.

Quick Start

Run the upgrade from the repository root to refresh pnpm locally and update CI pins.

Frequently Asked Questions about pnpm-upgrade

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

FAQPage Schema
How do I keep pnpm versions in sync between local development and GitHub Actions CI?

To keep pnpm in sync, this Skill updates pnpm locally via Corepack and aligns the packageManager field in package.json with the pnpm version pinned in your GitHub Actions workflows.

How do I pin the pnpm action-setup commit SHA in GitHub Actions workflows?

You can pin the pnpm action-setup commit SHA by running this Skill, which updates your workflow files to reference the specific commit SHA corresponding to your newly determined pnpm version.

What is the best way to upgrade pnpm and prepare Corepack across multiple repositories?

The best way to upgrade pnpm across repositories is using this Skill to determine the latest PNPM_VERSION, prepare Corepack, update package.json, and verify the toolchain changes.

Does this pnpm update process require manual verification of integrity hashes?

No manual verification is needed because the Skill automatically determines and applies the PNPM_INTEGRITY and PNPM_SHA512_HEX values during the Corepack preparation and upgrade process.

Can I use this to update the packageManager field in package.json to match a new pnpm release?

Yes, you can use this Skill to update the packageManager field in package.json, ensuring it matches the latest pnpm release and aligns with your CI workflow pins.