chore: update root dependencies

[tszhong0411]

Summary by CodeRabbit

• Chores
  • Updated development dependencies to their latest minor versions:
    • @cspell/dict-npm
    • knip
    • lint-staged
    • tsup

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1a3a8ab

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 27, 2025 2:54pm
honghongme	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 27, 2025 2:54pm

[coderabbitai]

Walkthrough

The pull request contains minor version updates for several development dependencies in the package.json file. These updates include incremental version bumps for @cspell/dict-npm, knip, lint-staged, and tsup packages. The changes are typical maintenance updates to ensure the project is using the latest patch versions of its development tools and dependencies.

Changes

File	Changes
package.json	- Updated @cspell/dict-npm from ^5.1.23 to ^5.1.24 - Updated knip from ^5.43.3 to ^5.43.5 - Updated lint-staged from ^15.4.2 to ^15.4.3 - Updated tsup from 8.3.5 to 8.3.6

---

🪧 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. (Beta)
• @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.

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)

package.json (1)

82-82: Consider using caret range for tsup.

Unlike other dependencies that use caret ranges (^), tsup is pinned to an exact version. This might make future updates more difficult to manage. Consider using a caret range unless there's a specific reason for version pinning.

-    "tsup": "8.3.6",
+    "tsup": "^8.3.6",

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 50329a7 and 1a3a8ab.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• package.json (2 hunks)

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

• GitHub Check: TypeScript
• GitHub Check: Tests
• GitHub Check: Knip
• GitHub Check: ESLint

🔇 Additional comments (1)

package.json (1)

Line range hint 58-82: LGTM! Minor version updates for development dependencies.

The changes contain patch version updates for development tools, which should be safe to apply.

Let's verify the changes by checking the changelogs and running the test suite:

✅ Verification successful

✅ Dependency updates verified successfully

All development dependencies were updated and verified through a successful build process across all workspace packages. No breaking changes or compatibility issues were detected.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the impact of dependency updates

# Install dependencies
pnpm install

# Run the test suite
pnpm test:unit
pnpm type-check
pnpm lint

# Check build output
pnpm build

Length of output: 43561