fix: disable husky in CI

[DaxServer]

Summary by CodeRabbit

• Chores
  • Updated workflow configuration to improve reliability of dependency installation during releases.
• Documentation
  • Enhanced README with additional badges displaying license, workflow status, package version, and publish date.

[coderabbitai]

Walkthrough

The release workflow was modified to disable Husky by setting HUSKY=0 in the environment and to run bun install with the --frozen-lockfile flag to prevent lockfile updates. The README header was updated to include multiple new badges showing license, workflow status, and npm package information. No changes were made to exported or public entities.

Changes

File(s)	Change Summary
.github/workflows/release.yml	Disabled Husky by setting HUSKY=0 environment variable; added --frozen-lockfile to bun install.
README.md	Replaced single badge with multiple badges: GitHub License, CodeRabbit PR Reviews, GitHub Actions lint status, and npm version and publish date.

Possibly related PRs

• feat(release): add provenance for GitHub Actions #2: Also modifies GitHub Actions release workflow but focuses on permissions and setup-bun version updates, related through workflow configuration changes.

Poem

In the warren, scripts run neat,
Husky naps, its job complete.
Bun installs with lockfile tight,
Ensuring builds are always right.
Rabbits cheer, the workflow’s clean—
Release day’s smooth, just as we mean! 🐇✨

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/release.yml (1)

33-33: Enforce lockfile integrity and improve performance
The --frozen-lockfile flag ensures the lockfile isn't modified during CI, which is excellent for reproducible builds. Consider adding a cache step (e.g., via actions/cache on ~/.bun) to speed up dependency installs in future runs.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 5053809 and 8647ad9.

📒 Files selected for processing (1)

• .github/workflows/release.yml (2 hunks)

🔇 Additional comments (1)

.github/workflows/release.yml (1)

15-16: Disable Husky in CI
Setting HUSKY: 0 disables Husky hooks during the CI run, preventing accidental pre-commit/pre-push scripts from blocking the pipeline.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

README.md (1)

3-3: Display npm package information
The badges for package version and last-published date are informative. For better UX, consider wrapping each badge in a markdown link to the npm package page so users can click through directly.

Example diff:

-[![NPM Version](https://img.shields.io/npm/v/%40geocoding-ai%2Fmcp)]
-[![NPM Last Update (with dist tag)](https://img.shields.io/npm/last-update/%40geocoding-ai%2Fmcp/latest?label=npm%20last%20published)]
+[![NPM Version](https://img.shields.io/npm/v/%40geocoding-ai%2Fmcp)](https://www.npmjs.com/package/%40geocoding-ai%2Fmcp)
+[![NPM Last Update (with dist tag)](https://img.shields.io/npm/last-update/%40geocoding-ai%2Fmcp/latest?label=npm%20last%20published)](https://www.npmjs.com/package/%40geocoding-ai%2Fmcp)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8647ad9 and c97dae4.

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

README.md

[style] ~1-~1: Using many exclamation marks might seem excessive (in this case: 4 exclamation marks for a text that’s 1217 characters long)
Context: ![NPM Version](https://img.shields.io/npm...

(EN_EXCESSIVE_EXCLAMATION)

🔇 Additional comments (2)

README.md (2)

1-1: Add license badge for project metadata
The MIT license badge is correctly configured via Shields.io and linked to the appropriate license page. This improves clarity around project licensing.

🧰 Tools

🪛 LanguageTool

[style] ~1-~1: Using many exclamation marks might seem excessive (in this case: 4 exclamation marks for a text that’s 1217 characters long)
Context: ![NPM Version](https://img.shields.io/npm...

(EN_EXCESSIVE_EXCLAMATION)

---

2-2: Surface CI and review status
Including both the CodeRabbit PR reviews badge and the GitHub Actions lint status badge gives immediate insight into code quality and build health—great addition.