Stabilize Release workflow PR creation by replacing gh pr create with REST API flow

[Copilot]

The Release workflow was failing after semantic-release completed because PR creation intermittently failed via GitHub CLI’s GraphQL path. This change hardens the PR-creation step and makes reruns safe.

• Root cause addressed

  • Release job failed at gh pr create with a GraphQL execution error, despite successful release branch creation/push.

• Workflow changes (.github/workflows/release.yml)

  • Replaced gh pr create with gh api REST call to POST /repos/{owner}/{repo}/pulls.
  • Added pre-check for an existing open PR on the release branch (head=owner:branch, base=master) to avoid duplicate PR attempts on reruns.
  • Kept release branch naming, commit content, and base branch behavior unchanged.

• Behavioral impact

  • Release step remains: semantic-release updates files → branch/commit/push → PR opened.
  • If a matching PR already exists, workflow logs and continues instead of failing.

EXISTING_PR_URL=$(gh api "repos/${{ github.repository }}/pulls?head=${{ github.repository_owner }}:${BRANCH_NAME}&base=master&state=open" --jq '.[0].html_url // empty')

if [[ -n "$EXISTING_PR_URL" ]]; then
  echo "Release PR already exists: ${EXISTING_PR_URL}"
else
  gh api --method POST "repos/${{ github.repository }}/pulls" \
    -f title="$PR_TITLE" -f body="$PR_BODY" -f head="$BRANCH_NAME" -f base="master"
fi

[Copilot]

Pull request overview

This PR hardens the release workflow’s “open a release PR” step by replacing gh pr create (GraphQL) with a REST-based gh api flow and adding an “existing open PR” pre-check to make reruns less error-prone.

Changes:

• Builds PR title/body as variables and creates the PR via POST /repos/{owner}/{repo}/pulls using gh api.
• Adds a pre-check for an existing open PR matching head=owner:branch and base=master to avoid duplicates on reruns.

---

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