chore: update devDependencies for commitizen, husky, and prettier

[maehr]

Pull request

Proposed changes

Types of changes

• New feature (non-breaking change which adds functionality).
• Enhancement (non-breaking change which enhances functionality)
• Bug Fix (non-breaking change which fixes an issue).
• Breaking change (fix or feature that would cause existing functionality to change).

Checklist

• I have read the README document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

Summary by CodeRabbit

• Chores
  • Updated development dependencies for improved performance and functionality, including commitizen, husky, and prettier.

[coderabbitai]

Walkthrough

The pull request includes updates to the package.json file, specifically in the devDependencies section. The versions of three packages have been incremented: commitizen from ^4.3.0 to ^4.3.1, husky from ^9.0.11 to ^9.1.6, and prettier from ^3.2.5 to ^3.3.3. No other changes were made to the file's structure or content.

Changes

File	Change Summary
package.json	Updated commitizen from ^4.3.0 to ^4.3.1, husky from ^9.0.11 to ^9.1.6, and prettier from ^3.2.5 to ^3.3.3.

Poem

In the garden where code does bloom,
Versions updated, dispelling the gloom.
Commitizen hops, Husky runs fast,
Prettier shines bright, the changes are cast.
With each little tweak, our project takes flight,
A dance of dependencies, oh what a sight! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between c6fec45 and 9c8bf97.

⛔ 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)

🧰 Additional context used

🔇 Additional comments (4)

package.json (4)

15-15: LGTM: commitizen version update

The update of commitizen from ^4.3.0 to ^4.3.1 is a minor patch update. This change is in line with the PR objectives and follows best practices for version management in package.json.

---

15-18: Overall assessment: Changes look good

The updates to commitizen, husky, and prettier in the devDependencies section are consistent with the PR objectives and follow best practices for version management in package.json. These minor version updates are unlikely to introduce breaking changes, but it's always a good idea to run the project's test suite after updating dependencies.

To ensure everything is working as expected after these updates, consider running the following checks:

#!/bin/bash
# Install dependencies and run tests (if available)
npm install
npm test

# Verify that the commit process still works
git commit --allow-empty -m "test: verify commitizen"

# Check if there are any new prettier formatting changes
npm run check

If all these checks pass, the PR should be safe to merge.

---

18-18: LGTM: prettier version update

The update of prettier from ^3.2.5 to ^3.3.3 is appropriate and aligns with the PR objectives. The change follows best practices for version management in package.json.

To ensure that this update doesn't introduce unexpected formatting changes, it would be prudent to run prettier on the codebase and verify the results:

#!/bin/bash
# Run prettier and check for any formatting changes
npm run check

If there are any formatting changes, they should be reviewed and potentially included in this PR.

---

17-17: LGTM: husky version update

The update of husky from ^9.0.11 to ^9.1.6 is appropriate and aligns with the PR objectives. The change follows best practices for version management in package.json.

Given the larger version jump compared to the other updates, it might be beneficial to review the changelog for any significant changes or new features:

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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 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.