Use RELEASE_PAT for changesets/action so Version Packages PRs trigger CI

[RhysSullivan]

Summary

Swap GITHUB_TOKEN for secrets.RELEASE_PAT (with fallback) in the changesets/action step of release.yml. Falls back to GITHUB_TOKEN when the secret is unset, so forks and pre-secret states keep working.

Why

GitHub does not trigger downstream workflow runs from events caused by the default GITHUB_TOKEN. The Version Packages PR auto-opened by changesets/action was being authored by github-actions[bot] via that token, so neither pkg-pr-new nor CI ran on it. Reviewers couldn't preview-install the bundle that was about to publish.

With a PAT, the PR is authored by a real user and downstream workflows fire normally.

Setup needed (one-time)

Repo secret RELEASE_PAT must be set to a PAT (fine-grained or classic) with at minimum:

• Contents: Read and write
• Pull requests: Read and write

Scoped to this repo only (for fine-grained PATs). Already set in this repo.

Test plan

• After merge, push a no-op changeset commit to main and confirm the resulting Version Packages PR has pkg-pr-new + CI runs without manual close/reopen

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	executor-cloud	1607db8	May 10 2026, 05:57 AM

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	executor-marketing	1607db8	Commit Preview URL Branch Preview URL	May 10 2026, 05:57 AM