chore: use corepack

[alexandre-abrioux]

This is a proposal to use Corepack to enforce Yarn's version, instead of yarn-path.

https://yarnpkg.com/configuration/yarnrc#yarnPath

The yarnPath setting used to be the preferred way to install Yarn within a project, but we now recommend to use Corepack in most cases.

Summary by CodeRabbit

• Chores

  • Enhanced build and testing workflows by integrating a step to enable the package management tool.
  • Specified the required package manager version to ensure consistent dependency handling.
  • Removed an outdated auto-generated configuration file to streamline setup.

• Documentation

  • Updated installation instructions to guide users in enabling the package management tool for optimal performance.

[coderabbitai]

Walkthrough

The pull request introduces a new reference in the CI configuration to enable Corepack by running sudo corepack enable in multiple jobs. The installation instructions in the README are updated accordingly. Additionally, the auto-generated Yarn configuration file (.yarnrc) is removed, and the package.json file is updated with a new "packageManager" property that specifies the Yarn version along with its checksum.

Changes

File(s)	Change Summary
.circleci/config.yml, README.md	Added Corepack-related changes: .circleci/config.yml now includes a new enable_corepack step (using sudo corepack enable) in multiple CI jobs; README.md adds installation instructions for enabling Corepack.
.yarnrc, package.json	Updated Yarn configuration: Deleted .yarnrc (previously auto-generated with Yarn directives) and added a new "packageManager" property in package.json with the specified Yarn version and checksum.

Sequence Diagram(s)

sequenceDiagram
    participant CI as CI Pipeline
    participant Corepack as Corepack Step
    participant Job as Subsequent Commands

    CI->>Corepack: Run `sudo corepack enable`
    Corepack-->>CI: Corepack enabled
    CI->>Job: Execute remaining job steps

Loading

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.circleci/config.yml (1)

38-41: Corepack Enable Anchor Configuration
The addition of the enable_corepack anchor (lines 38–41) is a great move toward DRYing up the configuration by centralizing the Corepack activation step. This ensures consistency across jobs. One minor consideration: verify if the use of sudo is required within your container environment—if not, removing it could simplify the command and reduce potential permission issues.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4597d37 and c31ecbe.

⛔ Files ignored due to path filters (1)

• .yarn/releases/yarn-1.22.19.cjs is excluded by !**/.yarn/**

📒 Files selected for processing (4)

• .circleci/config.yml (12 hunks)
• .yarnrc (0 hunks)
• README.md (1 hunks)
• package.json (1 hunks)

💤 Files with no reviewable changes (1)

• .yarnrc

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: build-and-test

🔇 Additional comments (3)

package.json (1)

9-9: Explicit Yarn Version Declaration
The new "packageManager" field precisely specifies the required Yarn version along with its checksum. This addition ensures that Corepack uses the correct version of Yarn across all environments.

README.md (1)

59-63: Enhanced Corepack Setup Instructions
The updated "Install" section now clearly instructs users to run corepack enable before installing dependencies, ensuring that the Yarn version matches what is specified in package.json. Consider adding a brief note that this step might require administrative privileges depending on the user’s environment.

.circleci/config.yml (1)

76-76: Consistent Reference Usage Across Jobs
The repeated usage of the *enable_corepack reference in multiple job steps (e.g., lines 76, 102, 117, 209, 233, 247, 263, 290, and 307) demonstrates a clean and maintainable approach. This approach minimizes duplication and helps ensure that Corepack is enabled uniformly across the entire CI pipeline.