Weekly Release Digest
Every week, AI reads every code change that reached our demo environment and tells our SEs what to demo.
# se-teamWeek of Oct 5
This week on demo: 3 to show, 2 to know
Demo this
- Saved views on the items tableLIVE
- Faster search on large projectsLIVE
- Bulk relink from the graphflag: bulkRelinkV2
Heads up
- Export dialog moved to the toolbar
- Older sync setting retired
A feature merged to main can be weeks from the demo environment, and telling the team to demo it early is how a digest loses credibility. Many features also ship behind settings that are off by default.
- A script diffs the demo environment's deploy history since the last digest, so it only reports what is live on demo.
- It reads PR numbers and titles straight from the merge commits, with no per-PR API calls.
- It saves where it stopped, so the next run has no gaps and no double-reporting.
- AI sorts each change into "Demo this" or "Heads up", tagged LIVE or with its exact flag name.
- Every "Demo this" item gets a beat: what to click, what the customer sees, one credible detail.
- It drafts a short Slack headline and a thread. I edit and post.
887PRs sorted across 5 digests
14sto parse merge commits, vs 5+ minutes of API calls
3.1 daysmedian time between demo deploys
- It saves me at least a few hours a week (my estimate).
- I used to read the release notes by hand, click into each change, and work out a demo flow for every new feature. The digest does all of that.
- 887 changes so far, boiled down to what to show and what to know. Features that are still switched off are named, so nobody demos them by mistake.