a307bd2e3d
- A release-blocker issue's text is never read: its author can edit it after a maintainer labels it, so an open blocker holds every beta, and one closed as completed still holds the betas published before it closed. - Even --force never promotes a beta that isn't newer than the stable release: horizon-server update and install.sh download GitHub's latest. - When the oldest beta newer than the stable release has waited 24 hours, promote.yml opens a "Promotion to stable has stalled" issue with the last reason; the next promotion closes it. - promote.yml: persist-credentials: false; issues: write for the stall issue. - Website: the newest 100 releases, plus GitHub's latest (the stable one) when a day of betas pushes it out. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>