chore: add override for brace-expansion in pnpm configuration

[muneebs]

Summary by CodeRabbit

• Chores
  • Updated package dependencies and configuration to newer versions.
  • Simplified linter rules by removing select style checks.

[coderabbitai]

Walkthrough

Lo! The scroll of package.json hath been inscribed anew, with the devDependencies for @biomejs/biome raised from "2.0.0-beta.1" unto "^2.1.2". Furthermore, the pnpm.overrides field now holdeth a binding for the package brace-expansion at version "^2.0.2". The tome of biome.jsonc too hath been updated: its schema version lifted to "2.1.2", and three linter edicts—noCommaOperator, useNumericLiterals, and noArguments—removed from the style commandments.

Changes

Files	Change Summary
package.json	Updated @biomejs/biome version to ^2.1.2; added pnpm.overrides for brace-expansion to ^2.0.2.
biome.jsonc	Bumped schema version to 2.1.2; removed three linter rules: noCommaOperator, useNumericLiterals, and noArguments.

Estimated code review effort

1 (~3 minutes)

Poem

Upon the scrolls of code and rule,
The versions climb, the rules grow cool.
brace-expansion bound with care,
And linter edicts trimmed with flair.
Small changes wrought with wizard’s grace,
To keep the build a steady place.
🧙‍♂️✨

---

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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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)

biome.jsonc (1)

78-79: A parchment is best ended with a gentle breeze, not abrupt silence.

The file closes without a trailing newline, which may vex certain tools and keepers of the code. Append one more empty line to soothe them.

-}
+}
+

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between bd77df9 and 384d97f.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (2)

• biome.jsonc (2 hunks)
• package.json (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• package.json

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Analyze

🔇 Additional comments (2)

biome.jsonc (2)

2-2: Hearken! The schema path now points to Biome 2.1.2 – keep thy tools in step.

The scroll now invokes "https://biomejs.dev/schemas/2.1.2/schema.json". Be sure the local Biome CLI and any CI images have been lifted to ≥ 2.1.2, else the linter will mutter in confusion and refuse its duties.

---

30-50: Several protective wards were quietly removed – was this thy intent?

The commandments noCommaOperator, useNumericLiterals, and noArguments have vanished. Without these runes, subtle perils may creep into the code. Confirm that their removal is a deliberate choice and, if so, that equivalent safeguards dwell elsewhere.