Fix semantic-release workflow blocked by repository protection rules

[itsJess1ca]

Resolves #6

Summary

• Configure release workflow to use RELEASE_PAT for repository rule bypass
• Update checkout step to use RELEASE_PAT when available
• Update semantic-release environment variables to use RELEASE_PAT
• Maintain fallback to GITHUB_TOKEN for backward compatibility

Problem Solved

The semantic-release workflow was failing with repository rule violations because GITHUB_TOKEN cannot bypass branch protection rules. The workflow could not push version bump commits and tags back to the protected main branch.

Solution

• Use RELEASE_PAT (Personal Access Token) with admin permissions
• Configure workflow to use RELEASE_PAT in all steps that interact with Git
• Enables semantic-release to bypass repository protection rules
• Maintains compatibility for environments without RELEASE_PAT configured

Testing

Once merged and RELEASE_PAT is configured as a repository secret, the release workflow should successfully:

• Push version bump commits to main branch
• Create and push git tags
• Publish package to npm
• Create GitHub releases

Generated with Claude Code

[Copilot]

Pull Request Overview

This PR fixes the semantic-release workflow by configuring it to use a Personal Access Token (RELEASE_PAT) to bypass repository protection rules that were blocking version bump commits and tag creation.

• Updates checkout action to use RELEASE_PAT when available with GITHUB_TOKEN fallback
• Configures semantic-release environment to use RELEASE_PAT for Git operations
• Updates workflow comments to reflect the new purpose of bypassing repository rules

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}