chore(deps-dev): Bump lefthook from 1.10.10 to 1.11.0

[dependabot]

Bumps lefthook from 1.10.10 to 1.11.0.

Release notes

Sourced from lefthook's releases.

v1.11.0

Changelog

• ef9a000bd28c8eb6a79f3677799ce0a1b642e0e9 docs(changelog): add links to users
• 45126bf9b1d11559594cc9c43d8d69e7ec4e625e perf: speed up git commands (#956)

v1.10.11

Changelog

• 358b1ced55d0a8ad7712680d68ce60ed56c2171e ci: use ubuntu-latest for gh-pages publish workflow
• 2f59812baaff99db8718a3e831c8c6f3ece6bed0 deps: bump github.com/briandowns/spinner from 1.23.1 to 1.23.2 (#935) (#940)
• 7b6e8817e12c925ba56d65701c76b9607ea5e780 deps: bump github.com/spf13/cobra from 1.8.1 to 1.9.1 (#952) (#958)
• a4ae15c0ab6091ee63d1e791ecca1135ac0fc2d1 fix(jsonschema): add $schema property (#942)

Changelog

Sourced from lefthook's changelog.

1.11.0 (2025-02-23)

• perf: speed up git commands (#956) by @​judofyr

1.10.11 (2025-02-21)

• deps: bump github.com/spf13/cobra from 1.8.1 to 1.9.1 (#952) (#958) by @​mrexox
• fix: add $schema property (#942) by @​mst-mkt
• deps: bump github.com/briandowns/spinner from 1.23.1 to 1.23.2 (#935) (#940) by @​mrexox

Commits

• 8a7f844 1.11.0: improve performance
• ef9a000 docs(changelog): add links to users
• 45126bf perf: speed up git commands (#956)
• 632c4cf 1.10.11: add $schema attribute and update deps
• 7b6e881 deps: bump github.com/spf13/cobra from 1.8.1 to 1.9.1 (#952) (#958)
• a4ae15c fix(jsonschema): add $schema property (#942)
• 6ad8b52 docs: fix templates override example lefthook-local.yml (#951)
• 358b1ce ci: use ubuntu-latest for gh-pages publish workflow
• d87b8d4 docs: describe the unusual behaviour of ** in glob option (#941)
• 2f59812 deps: bump github.com/briandowns/spinner from 1.23.1 to 1.23.2 (#935) (#940)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

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

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]

The code change is a simple update to the lefthook dependency version in the package.json file. Here's a quick review:

Changes:

• The lefthook dependency version has been updated from ^1.10.10 to ^1.11.0.

Observations:

1. Version Update: The update from ^1.10.10 to ^1.11.0 is a minor version bump. This typically includes backward-compatible new features or improvements.
2. Semantic Versioning: The use of ^ (caret) in the version specifier means that npm will install the latest version that is compatible with 1.11.0 (i.e., any version >=1.11.0 and <2.0.0).

Recommendations:

1. Check for Breaking Changes: Although minor versions are generally backward-compatible, it's good practice to review the lefthook changelog or release notes for 1.11.0 to ensure there are no breaking changes or new behaviors that could affect your project.
2. Test After Update: After updating the dependency, run your tests and ensure that the new version works as expected with your existing codebase.

Conclusion:

The change is straightforward and appears to be a routine dependency update. Just ensure that the new version is compatible with your project by reviewing the release notes and running your tests.