History

diffwireauto 608ac80b6a chore(#1137 ): cut 1.8.0+69 (production) Version bump to 1.8.0+69 and the owner-approved release texts: CHANGELOG [1.8.0], release-notes/1.8.0.md (the GitHub release body), play/1.8.0.txt (441/500), discord/1.8.0.md, and announcements/1.8.0.md for the GitHub Discussions Announcements category, with a README for the new folder. Every known issue that ships is listed: #1121, #1123, #1132, #1124, #1028 and #1134, plus #1066 in the CHANGELOG. Release tracker #1136, part of epic #312. Agent: JadeEagle (session e9df9ed6) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	3 days ago
..
1.8.0.md	chore(#1137 ): cut 1.8.0+69 (production)	3 days ago
README.md	chore(#1137 ): cut 1.8.0+69 (production)	3 days ago

diffwireauto 608ac80b6a chore(#1137 ): cut 1.8.0+69 (production)

Version bump to 1.8.0+69 and the owner-approved release texts:
CHANGELOG [1.8.0], release-notes/1.8.0.md (the GitHub release body),
play/1.8.0.txt (441/500), discord/1.8.0.md, and announcements/1.8.0.md
for the GitHub Discussions Announcements category, with a README for the
new folder.

Every known issue that ships is listed: #1121, #1123, #1132, #1124,
#1028 and #1134, plus #1066 in the CHANGELOG.

Release tracker #1136, part of epic #312.

Agent: JadeEagle (session e9df9ed6)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

1.8.0.md

chore(#1137 ): cut 1.8.0+69 (production)

README.md

chore(#1137 ): cut 1.8.0+69 (production)

README.md

GitHub Discussions announcement

One file per release: announcements/<version>.md, e.g. announcements/1.8.0.md.

Style

A post for the Announcements category of this repo's GitHub Discussions. It's for people who follow the project on GitHub: what landed, anything to read before updating, every known issue that ships, and where to get each platform. Plainer than the Discord text, shorter than the release notes, and it links to the release page for the full notes.

The first line gives the discussion title (**Title:** ...), followed by a --- line. The post body is everything after that.

The post goes up after the release is published, because it links to the release page. Only the owner posts it, or an agent on the owner's word. CI never posts it, and the release gate (.github/scripts/release-gate.sh) does not check this file.