feat: Add nightly cleanup of stale draft releases

[charlesvien]

Problem

Draft releases left behind by failed or aborted release runs accumulate over time and clutter the releases page.

Changes

1. Add cleanup-draft-releases.yml workflow
2. Schedule nightly at 00:00 UTC plus workflow_dispatch for manual runs
3. List releases via gh api --paginate and filter drafts with created_at older than 24 hours
4. Delete each match via DELETE /releases/{id}
5. Use default GITHUB_TOKEN with contents: write, no extra secrets required

How did you test this?

I did not

Publish to changelog?

[charlesvien]

• fix: Buffer feature-flag subscribers registered before init #2267 : 2 dependent PRs (#2268 , #2270 )
• feat: Add nightly cleanup of stale draft releases #2239 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Prompt To Fix All With AI

Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 2
.github/workflows/cleanup-draft-releases.yml:22-23
Without `set -o pipefail`, if `gh api --paginate` fails (e.g., auth error, rate limit, network issue), bash reports the exit status of the last command in the pipeline — the `while` loop — which exits 0 on empty input. The step passes silently with no releases deleted and no error surfaced, making failures completely invisible in CI logs.

```suggestion
        run: |
          set -o pipefail
          CUTOFF=$(date -u -d "1 hour ago" +%Y-%m-%dT%H:%M:%SZ)
```

### Issue 2 of 2
.github/workflows/cleanup-draft-releases.yml:18-23
**1-hour cutoff can delete in-progress release drafts**

The `code-release.yml` workflow builds macOS and Windows packages in parallel, each of which can take 30–60+ minutes before `finalize-release` un-drafts the release. When this cleanup is triggered via `workflow_dispatch` at e.g. 1:15 AM UTC and a release started at midnight, the draft would be ~1 hr 15 min old and fall inside the deletion window, mid-build. Consider raising the threshold to something like 24 hours (or at least 3–4 hours) since the scheduled run is daily anyway, which removes the risk without any real downside for stale-draft cleanup.

_{Reviews (1): Last reviewed commit: "Add nightly cleanup of stale draft relea..." | Re-trigger Greptile}

[adboio]

I did not

pog