fix: disable husky install when doing semantic release

[abest-tz]

Otherwise husky install fails with an obscure error about no .git directory existing.

Summary by CodeRabbit

• Chores
  • Updated the publishing workflow configuration to optimize the release process.

[coderabbitai]

Walkthrough

Adds a HUSKY environment variable set to "0" in the npm-publish job's Semantic Release step within the GitHub Actions workflow. This explicitly disables Husky installation during the package publication process.

Changes

Cohort / File(s)	Summary
CI/CD Configuration .github/workflows/publish.yml	Added HUSKY environment variable set to "0" to disable Husky installation during the semantic-release step in the npm-publish job.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: disabling Husky during semantic release in the publish workflow.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/enable_ssl

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[deepsource-io]

Here's the code health analysis summary for commits 308af47..b0a4858. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[github-actions]

🎉 This PR is included in version 5.7.1 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀