feat: add release token to release-please action in python.yml

[twangodev]

No description provided.

[coderabbitai]

Warning

Rate limit exceeded

@twangodev has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 11 minutes and 20 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.

✨ 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

---

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.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Copilot]

Pull request overview

Adds an explicit authentication token to the release-please GitHub Action in the Python CI workflow, likely to use a PAT/fine-grained token instead of the default GITHUB_TOKEN.

Changes:

• Configures googleapis/release-please-action@v4 to use ${{ secrets.RELEASE_TOKEN }} via the with.token input.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

secrets.RELEASE_TOKEN is not a default GitHub-provided secret; if it isn't configured in the repo/org, this workflow will fail at runtime. Consider either (a) using ${{ secrets.RELEASE_TOKEN || secrets.GITHUB_TOKEN }} as a fallback, or (b) adding repo documentation/onboarding notes that this secret must be created and what minimal scopes it needs (fine-grained PAT with contents/pull-requests write, etc.).

Suggested change

	token: ${{ secrets.RELEASE_TOKEN }}
	token: ${{ secrets.RELEASE_TOKEN || secrets.GITHUB_TOKEN }}