ci: fix release-pr-approvals for forks (#1150)

Follow-up for #1144.

Release please PRs are never created from forks, so running on
`pull_request_review` (which has only readonly access for PRs from
forks) will never need to post a commit status. Such cases are skipped
now instead of failing (i.e.
[here](https://github.com/a2aproject/a2a-js/actions/runs/30247915633/job/89919011242?pr=602)).

Author: ishymko

.github/workflows/release-pr-approvals.yml

@@ -37,6 +37,19 @@ jobs:
             const pr = context.payload.pull_request;
             const { owner, repo } = context.repo;
 
+            // pull_request_review runs on a fork PR get a read-only GITHUB_TOKEN,
+            // so createCommitStatus would 403. Release PRs are always created in
+            // this repo (release-please pushes release-please--* to the base repo,
+            // never a fork), so their review events keep a write token. Every other
+            // PR already gets its status from the pull_request_target run, which
+            // has a write token even for forks. So skip fork review events.
+            const isReviewEvent = context.eventName === 'pull_request_review';
+            const isFork = pr.head.repo?.full_name !== `${owner}/${repo}`;
+            if (isReviewEvent && isFork) {
+              core.info('Fork review event has a read-only token; status handled by pull_request_target.');
+              return;
+            }
+
             const setStatus = (state, description) =>
               github.rest.repos.createCommitStatus({
                 owner, repo, sha: pr.head.sha, context: CONTEXT, state, description,