Skip to content

chore: replace yarn with pnpm#421

Open
JustMell0 wants to merge 1 commit intopodman-desktop:mainfrom
JustMell0:task-399/use-pnpm
Open

chore: replace yarn with pnpm#421
JustMell0 wants to merge 1 commit intopodman-desktop:mainfrom
JustMell0:task-399/use-pnpm

Conversation

@JustMell0
Copy link
Copy Markdown

Migrate from yarn v1 to pnpm

  • Replace yarn with pnpm in all CI workflows (pr-check, build-next, release)
  • Use pnpm/action-setup with actions/setup-node cache integration
  • Add packageManager field to package.json
  • Replace yarn.lock with pnpm-lock.yaml

Closes #399

Signed-off-by: Dias Tursynbayev <original.justmello1337@gmail.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 5, 2026

Warning

Rate limit exceeded

@JustMell0 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 56 minutes and 59 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 040dc64b-c7bd-4c99-a8f1-b2e689bf9e39

📥 Commits

Reviewing files that changed from the base of the PR and between db2a3ee and 05c7d24.

⛔ Files ignored due to path filters (2)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (4)
  • .github/workflows/build-next.yaml
  • .github/workflows/pr-check.yaml
  • .github/workflows/release.yaml
  • package.json
📝 Walkthrough

Walkthrough

The PR migrates CI/CD pipelines and package manager configuration from Yarn v1 to pnpm. Three GitHub Actions workflows are updated to install and use pnpm via pnpm/action-setup, configure Node caching for pnpm, and run pnpm commands. The package.json declares pnpm@10.28.0 as the required package manager.

Changes

Package Manager Migration to pnpm

Layer / File(s) Summary
Package Manager Declaration
package.json
Adds packageManager field specifying pnpm@10.28.0 with integrity hash.
CI Workflow Updates
.github/workflows/build-next.yaml, .github/workflows/pr-check.yaml, .github/workflows/release.yaml
All three workflows replace Yarn-based steps with pnpm: remove Yarn cache discovery and caching logic, add pnpm/action-setup, configure Node caching for pnpm, and replace npx yarn commands with pnpm equivalents.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title 'chore: replace yarn with pnpm' accurately and concisely summarizes the main change of migrating from yarn to pnpm across CI workflows and package configuration.
Description check ✅ Passed The description provides relevant details about the changeset, including the migration from yarn to pnpm, updates to CI workflows, and configuration changes to package.json.
Linked Issues check ✅ Passed The pull request successfully addresses issue #399 by migrating the repository from Yarn v1 to pnpm, including CI workflow updates and package.json configuration.
Out of Scope Changes check ✅ Passed All changes are directly related to the pnpm migration objective. Updates to CI workflows and package.json configuration are within scope for the stated goal.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@JustMell0 JustMell0 force-pushed the task-399/use-pnpm branch from db2a3ee to 05c7d24 Compare May 5, 2026 13:46
Copy link
Copy Markdown
Contributor

@jeffmaury jeffmaury left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needs more love as build is failing

@JustMell0
Copy link
Copy Markdown
Author

Needs more love as build is failing

The build says:

/home/runner/work/extension-layers-explorer/extension-layers-explorer/src/explorer.spec.ts
Error:   177:15  error  'toThrowError' is deprecated  sonarjs/deprecation

which is out of scope of this PR. I could open a new one to fix this issue :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

update to pnpm

2 participants