fix(release): use local commits for release window

[hshoff]

Why use local commits for the release window?

The push workflow for PR #2021 still failed in the release step after retrying GitHub's compare endpoint three times.

The workflow checks out full git history with fetch-depth: '0', so the release script does not need the compare endpoint just to enumerate commit SHAs between the latest reachable tag and HEAD.

💥 Breaking Changes

• None.

🚀 Enhancements

• None.

📝 Documentation

• None.

🐛 Bug Fix

• Use local git rev-list --reverse <tag>..HEAD output to build the release commit window instead of fetching the same commit list from GitHub's compare endpoint.

🏠 Internal

• Keep GitHub API usage for commit-to-PR lookup, release creation, and release comments, where GitHub metadata is still needed.

Validation

• yarn lint
• git diff --check

[Copilot]

Pull request overview

This PR hardens the release workflow by removing reliance on GitHub’s compare endpoint for enumerating commits in the release window, instead deriving the commit list locally from the checked-out git history.

Changes:

• Switch release commit enumeration to git rev-list --reverse <tagSha>..HEAD rather than GET /compare.
• Update the release script call sites to use the new fetchCommitsSinceTag(tagSha) signature (no GitHub client required).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
scripts/performRelease/index.ts	Updates callers to use the local commit-window helper (no Octokit client passed).
scripts/performRelease/fetchCommitsSinceTag.ts	Replaces GitHub compare API usage with a local git rev-list-based implementation returning a compatible { data: { commits } } shape.

---

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