fix(ci): use GH_PAT to create release so publish workflow is triggered

[callumreid]

Summary

Releases created by GITHUB_TOKEN cannot trigger other workflows (GitHub security restriction). Switching to GH_PAT allows the on: release trigger in publish.yml to fire.

Secret required

GH_PAT must be set in repo secrets (Settings → Secrets → Actions) with Contents + Actions write permissions — already done.

Fixes

• Fixed CI release workflow to use GH_PAT instead of GITHUB_TOKEN, enabling the on: release trigger in publish.yml to execute (GitHub security restriction prevents GITHUB_TOKEN from triggering other workflows)

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: b17a98f7-1fa1-42e5-b402-5a057431d16b

📥 Commits

Reviewing files that changed from the base of the PR and between 77c6ed5 and 1928808.

📒 Files selected for processing (1)

• .github/workflows/release-please.yml

---

Walkthrough

The GitHub Actions workflow file release-please.yml was updated to change the authentication mechanism used during the release process. The GH_TOKEN environment variable now references secrets.GH_PAT instead of secrets.GITHUB_TOKEN. This is a straightforward substitution with no modifications to conditional logic or execution flow.

🚥 Pre-merge checks | ✅ 1

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	Title follows Conventional Commits format with 'fix' type and 'ci' scope, clearly describing the main change of switching from GITHUB_TOKEN to GH_PAT.

_{✏️ 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/pat-release

---

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