fix(release): space automatic nightlies at least six hours apart

[t3dotgg]

Automatic nightlies currently run every three hours. A merge just after a check waits another three hours, while a manual nightly can be followed by an automatic release soon after.

Check every 30 minutes in the existing release workflow. Build only when the candidate commit is ahead of the last published nightly and at least six hours have passed since publication. The existing concurrency queue serializes nightlies, so scheduled runs check the gap after any active nightly finishes. Manual releases still bypass these checks.

Validation: 10 focused tests pass and run in CI. Targeted lint and formatting pass. Workflow validation passes with existing unsupported runner labels, queue, and github.run_started_at warnings excluded. No release was dispatched.

Created with GPT-6 Astra in Codex.

Note

Add shouldReleaseNightly helper to space nightly releases six hours apart

Adds an exported async helper in check-nightly-release.cjs that lists all repo releases via GitHub pagination and finds the most recent nightly tag (current or legacy nightly-v format). The candidate workflow is allowed to release only when no qualifying nightly exists, at least six hours have passed since the last nightly, and the candidate SHA is ahead of the published tag.

• Risk: GitHub API failures now propagate instead of being swallowed; callers must handle the rejection.

^{Macroscope summarized 5a88801.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This changes the automatic release cadence and adds a runtime gate that can skip desktop, npm, GitHub Release, and Vercel nightly publishing. The logic is tested and focused, but the release/deployment behavior warrants human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.6 KiB	13.6 KiB	+6 B (+0.0%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	+8 B (+0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.6 KiB	6.6 KiB	−2 B (−0.0%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.1 KiB	57.1 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.6 KiB	+2 B (+0.0%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	−2 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.5 KiB	+4 B (+0.1%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.8 KiB	57.8 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	9	9	0 (0.0%)	21	✅

Baseline: e5d086c · PR result: 5a88801 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 113.8 KiB
• Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Bugbot is paused — on-demand spend limit reached

Bugbot uses usage-based billing for this team and has hit its on-demand spend limit.

A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue.