ci: disable husky in the release job so semantic-release can commit

[RonenMars]

Problem

The Release job has been failing on main — for PR #7 (RN engine) and PR #8 (match layout) — so nothing has published to npm: the registry is still at 1.2.0 despite two merged feat PRs that should have shipped 1.3.0.

Root cause is not npm auth.
@semantic-release/git makes a chore(release): <v> commit whose body is the generated changelog, and husky's commit-msg hook fires in CI.
commitlint then rejects the commit:

git commit -m chore(release): 1.3.0 [skip ci]
✖ footer's lines must not be longer than 100 characters [footer-max-line-length]
husky - commit-msg script failed (code 1)

Changelog lines embed GitHub commit + issue URLs, which are well over 100 chars — so effectively every release commit trips the rule, and the version bump + npm publish never run.

Fix

Set HUSKY: 0 on the Release step's env, so husky hooks are disabled for the auto-generated release commit only.
commitlint still guards human commits everywhere else (local hooks + PR title checks are untouched).

      - name: Release
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
          HUSKY: 0
        run: npx semantic-release

Effect once merged

The Release job on main succeeds and semantic-release publishes the pending 1.3.0 (the merged RN engine + match-layout work).
This PR itself is ci: scope — no bump — it just unblocks the pipeline.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
one-more-highlight-playground	Ignored		Jul 11, 2026 3:54pm

[github-actions]

🎉 This PR is included in version 1.3.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀