chore: migrate from npm to Yarn v4#1489
Open
planning-center-cloud-agent[bot] wants to merge 2 commits into
Open
chore: migrate from npm to Yarn v4#1489planning-center-cloud-agent[bot] wants to merge 2 commits into
planning-center-cloud-agent[bot] wants to merge 2 commits into
Conversation
Standardize on Yarn v4 as the package manager (API-106). - Add packageManager field pinning yarn@4.14.1 - Add .yarnrc.yml with node-modules linker and PCO npm registry - Replace package-lock.json with yarn.lock; drop .npmrc - Update .gitignore for yarn v4 conventions - Update CLAUDE.md setup instructions The CI workflow (.github/workflows/issue-triage.yml) still uses npm ci and must be switched to yarn separately — the GitHub App lacks the `workflows` permission to modify it in this PR. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
package-lock.json was removed in favor of yarn.lock, so `npm ci` would fail with no lockfile the next time an issue is opened. Enable Corepack, cache/install via yarn, and drop the now-unused npm registry-url input (the workflow-level YARN_NPM_REGISTRY_SERVER env var already routes yarn through the quarantine proxy).
jahammo2
approved these changes
Jul 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Migrates
developersfrom npm to Yarn v4 (yarn@4.14.1), part of the API team's package-manager standardization (API-106, this issue API-110).Changes
packageManagerfield topackage.jsonpinningyarn@4.14.1(managed via Corepack).yarnrc.ymlwithnodeLinker: node-modules,enableScripts: false, approved PCO git repos, and the PCO npm registry (matchingapi/pco-add-on-democonventions)package-lock.jsonwithyarn.lock.npmrc(registry now lives in.yarnrc.yml).gitignorefor Yarn v4 conventionsCLAUDE.mdsetup instructions (npm ci→yarn install).github/workflows/issue-triage.ymlto install via Yarn: add acorepack enablestep, switchsetup-nodecache fromnpmtoyarn, and replacenpm ciwithyarn install --immutable(the workflow-levelYARN_NPM_REGISTRY_SERVERenv var already points yarn at the quarantine proxy, so no new registry config was needed)This closes a gap from the original version of this PR, where
package-lock.jsonwas removed but CI still rannpm ci— that combination would have broken the workflow (npm cihard-fails without a lockfile) the next time an issue was opened after merge. The workflow is now updated in this same PR so there's no window where auto-triage is broken.Test plan
yarn installgenerates a validyarn.lockyarn install --immutablepasses (verifies lockfile is in sync — what CI will run)node_modules(@anthropic-ai/sdk,@actions/core,@actions/github)🤖 Generated with Claude Code