v2.2.0 ·
Releases now show up where you can see them
Every aidlc release creates a GitHub release. You have never seen one.
The source repo is private, so its releases page is a 404 for everyone but me. The release notes GitHub writes for it are worse than invisible: they list pull request titles and link to pages you cannot open. The one public place you can watch is the feedback repo, rasensio/aidlc-feedback, and until now nothing told it a release had happened. You found out from npm, if you looked.
What changed
When a release goes out, the release workflow now posts one discussion in the Announcements category of the feedback repo. It holds the version, the opening lines of that release's post on this blog, a link to the post, and a link to the version on npm. Nothing else. A reply to it lands where feedback already goes.
You can see what it would post without posting anything:
node packages/website/scripts/announce-release.mjs --tag v2.1.0 --dry-run
Why this way
The announcement is built from the blog post, not from GitHub's release notes. The post is already public and already passed the check that keeps local paths and tokens out of this site. The announcement runs that check again before it sends, and refuses any link that is not the post or npm.
A release with no blog post announces nothing. That is the noise filter. Fifteen versions shipped between 1.88.0 and 2.1.0, and a channel that gets a post for each one stops being read.
Posting can never fail a release. The packages are on npm by the time this step runs, so if GitHub refuses the post, the step shows red and the release stays green. A rerun checks for an announcement with that version first, so it does not post twice.
What it does not do yet
It needs a token that can write to the feedback repo's Discussions, and that token does not exist yet. Until I create it, every release prints one line saying the announcement was skipped. So this release is not announced by the thing it ships. The first real post is the release after the token is set, and no test here has seen GitHub accept one.
It also does not back-fill. The releases before this one stay unannounced.