deps: Upgrade @biomejs/biome,@types/shelljs,cspell and lefthook

[hustcer]

deps: Upgrade @biomejs/biome,@types/shelljs,cspell and lefthook

Summary by CodeRabbit

• Chores
  • Updated several development tools and libraries to their latest versions for improved stability and compatibility.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This change updates several development dependencies in the package.json file, increasing their version numbers. No other modifications are made to scripts, dependencies, or configuration fields. The update is limited to version bumps for devDependencies only.

Changes

File(s)	Change Summary
package.json	Bumped devDependencies: @biomejs/biome, @types/node, @types/shelljs, cspell, and lefthook to newer versions.

Possibly related PRs

• deps: Upgrade @octokit/rest and @types/node #150: Updates the version of @types/node in package.json, similar to this PR's devDependency management.
• deps: Upgrade cspell,lefthook,semver, etc. #148: Updates overlapping devDependencies (cspell, lefthook, @types/node) in package.json via version bumps.
• deps: Upgrade @biomejs/biome and cspell #154: Upgrades development dependencies including @biomejs/biome and cspell, directly aligning with this PR's focus.

Poem

Up hopped a rabbit, quick to see,
DevDependencies fresh as can be!
Biome, cspell, and lefthook too,
All got a shiny version renew.
No scripts were changed, no configs in sight—
Just numbers bumped, all versions right!
🐇✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f65679f and 80df21d.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• package.json (1 hunks)

---

🪧 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.

[github-actions]

Code Analysis

• Key observations:
  • Dependency version updates across multiple packages including BiomeJS, Node types, ShellJS types, cspell, and lefthook
  • All updates appear to be minor/patch version bumps following semantic versioning
  • No major breaking changes introduced based on version numbers
  • Maintained consistent versioning strategy with caret (^) notation

Security Review

• Vulnerability findings:
  • No immediate security vulnerabilities found in the updated packages
  • Recommended to verify changelogs for @biomejs/biome 2.1.1 and cspell 9.1.5 for any security-related fixes
  • ShellJS type definitions update (0.8.16 → 0.8.17) might include security-related type improvements

Optimization Suggestions

• Performance improvements:
  • Consider auditing if newer versions of these devDependencies offer any performance benefits (particularly BiomeJS and cspell)
  • Verify if newer TypeScript version (5.8.3) offers compilation performance improvements
  • Potential to explore if newer BiomeJS version provides faster linting/formatting

Overall Quality: 4