fix: token for publishing

[ilan-phantom]

Summary by CodeRabbit

• Chores
  • Updated release workflow authentication handling to ensure publishing credentials are managed correctly.
  • Added a repository security configuration setting to disable code-owner approval enforcement.

---

This release contains no user-facing changes; updates are limited to internal build and repository configuration.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Modified GitHub Actions release workflow to unset token values for Setup Node.js and to add empty NODE_AUTH_TOKEN and NPM_TOKEN env vars in the release job. Added security.yaml with codeowner_approvals: false.

Changes

Cohort / File(s)	Summary
GitHub Actions Release Workflow .github/workflows/release.yml	Set token to "" in the Setup Node.js step and added environment overrides in the Create Release step: NODE_AUTH_TOKEN: "", NPM_TOKEN: "", retained GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}; comment notes trusted publishing behavior.
Security Configuration security.yaml	Added new file with codeowner_approvals: false.

🚥 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 'fix: token for publishing' directly addresses the main changes in the PR, which involve fixing token configuration in the release workflow for npm publishing.
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.}

---

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