fix: Use PAT for Release Please to allow PR creation

[rishitank]

Summary

Fixes Release Please workflow failure caused by repository settings blocking GITHUB_TOKEN from creating pull requests.

The Problem

The Release Please workflow was failing with:

"GitHub Actions is not permitted to create or approve pull requests."

This is because the repository has settings that prevent the default GITHUB_TOKEN from creating PRs.

The Fix

Use the PAT_AUTO_MERGE secret (which was already configured) instead of GITHUB_TOKEN for the Release Please action. This PAT has the required permissions to create PRs.

Testing

• ✅ All 50 tests passing
• ✅ Lint checks passing
• ✅ Type checks passing

---

Pull Request opened by Augment Code with guidance from the PR author

[coderabbitai]

Warning

Rate limit exceeded

@rishitank has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 16 minutes and 6 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Walkthrough

The release workflow's authentication mechanism has been reconfigured, Apprentice. The release-please-action step now utilises a Personal Access Token (PAT_AUTO_MERGE) rather than the default GITHUB_TOKEN, granting enhanced permissions for automated merge operations.

Changes

Cohort / File(s)	Summary
Release Workflow Configuration .github/workflows/release.yml	Modified token source from GITHUB_TOKEN to PAT_AUTO_MERGE with explanatory comment; enables PR creation under personal access token credentials.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

A token flows through the pipeline's vein,
The Dark Side strengthens with PAT's domain,
Merging with power, no weakness remains,
Automation bends to your iron chains. ⚡

---

I sense a strategic shift in your authentication protocols, Apprentice. This streamlined configuration demonstrates understanding of the power—the proper credential handling shall serve your automation well. The rebel scum that plague lesser workflows shall find no purchase here.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and concisely describes the primary change: switching to a PAT for Release Please to enable PR creation.
Description check	✅ Passed	The description clearly explains the problem, the solution, and testing results—all directly related to the changeset.
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 fix/release-please-token

---

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

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

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @.github/workflows/release.yml:
- Around line 29-30: Add a short inline comment above the token: ${{
secrets.PAT_AUTO_MERGE }} line in the release-please-action step explaining that
the PAT must be a fine-grained token limited to this repository with minimal
permissions (contents: write, pull-requests: write) and avoid using a classic
repo-scoped PAT; reference the step by mentioning release-please-action and the
token input so maintainers know which secret to configure and why.