fix(release): retry GitHub compare requests

[hshoff]

Why retry release compare requests?

The push workflow for feat(tooltip): add Floating UI tooltip primitives (#2020) failed in the release step while fetching commits from GitHub's compare endpoint.

This PR hardens that fetch path so transient GitHub response/body failures use the same retry helper as the rest of the release metadata requests.

💥 Breaking Changes

• None.

🚀 Enhancements

• None.

📝 Documentation

• None.

🐛 Bug Fix

• Retry the release compare request used to fetch commits since the latest tag.
• Treat transient GitHub request failures such as Premature close, socket resets, timeout-style errors, and 5xx responses as retryable.

🏠 Internal

• Reuse the release script's existing GitHub request retry helper for fetchCommitsSinceTag.

Validation

• yarn lint
• git diff --check

[Copilot]

Pull request overview

This PR hardens the release automation’s GitHub compare request path by routing the compare call through the existing retry helper and expanding the helper’s definition of retryable failures to include common transient network and 5xx errors.

Changes:

• Expand runGithubRequestWithRetries to retry on GitHub 5xx responses and common transient network/body failures (in addition to rate limiting).
• Update fetchCommitsSinceTag to use runGithubRequestWithRetries for the compare endpoint call.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
scripts/performRelease/runGithubRequestWithRetries.ts	Broadens retry detection beyond rate limits to include 5xx + transient network/body errors; updates warning message accordingly.
scripts/performRelease/fetchCommitsSinceTag.ts	Wraps the GitHub compare request in the shared retry helper to avoid transient failures breaking releases.

---

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