chore: upgrading husky version and removed husky's deprecated things

[abhijeetw035]

📋 Description

JIRA ID:

Upgraded husky from version ^9.0.11 to ^9.1.7 to align with the latest stable release.
Removed deprecated bootstrap lines from .husky/commit-msg and .husky/pre-commit hook scripts, as these are no longer required in newer Husky versions.

---

✅ Type of Change

• 🐞 Bug fix (non-breaking change which resolves an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 🔥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 🛠 Refactor (change that is neither a fix nor a new feature)
• ⚙️ Config change (configuration file or build script updates)
• 📚 Documentation (updates to docs or readme)
• 🧪 Tests (adding new or updating existing tests)
• 🎨 UI/UX (changes that affect the user interface)
• 🚀 Performance (improves performance)
• 🧹 Chore (miscellaneous changes that don't modify src or test files)

---

ℹ️ Additional Information

Tested by making a sample commit and verifying that:

• lint-staged ran correctly via the pre-commit hook.
• commitlint successfully validated the commit message format.

No errors or warnings were observed during the commit process.

Summary by CodeRabbit

• Chores
  • Simplified commit message and pre-commit hook scripts for improved maintainability.
  • Updated Husky to the latest version for enhanced tooling support.
  • Renamed GitHub Actions workflow to "Commit Compliance" for clearer purpose.

[coderabbitai]

Walkthrough

This update simplifies the Husky Git hook scripts by removing the shell shebang and Husky environment sourcing from both .husky/commit-msg and .husky/pre-commit. The scripts now directly invoke their respective commands (commitlint and lint-staged) without additional setup. Additionally, the husky package version in package.json was updated from ^9.0.11 to ^9.1.7. The GitHub Actions workflow name was changed from "Lint Commit Messages" to "Commit Compliance" without altering its logic.

Changes

File(s)	Change Summary
.husky/commit-msg, .husky/pre-commit	Removed shell shebang and Husky helper sourcing; scripts now directly call their commands.
package.json	Updated husky devDependency version from ^9.0.11 to ^9.1.7.
.github/workflows/commit-lint.yml	Renamed workflow from "Lint Commit Messages" to "Commit Compliance" without other changes.

Possibly related PRs

• feat(git-hooks): setup Commitlint, Husky, and Commitizen for standardized commit messages #62 #94: Introduced the original Husky commit-msg hook with commitlint setup, which is now being simplified in this PR.

Poem

A rabbit hopped to tidy code,
Husky hooks shed their heavy load.
No more shebangs, no sourced shell,
Just simple scripts that work so well.
With Husky new and scripts so neat,
This update is a coder’s treat! 🐇✨

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

📜 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 6b65579 and 091b073.

📒 Files selected for processing (1)

• .github/workflows/commit-lint.yml (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• .github/workflows/commit-lint.yml

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

• GitHub Check: Build

---

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud