Release notes drafted every day, published when you say.
Merged pull requests become a changelog draft: one release per day, a plain-language title, Keep-a-Changelog categories, each bullet citing the PRs it came from and, where a passing run took one, a screenshot. A person publishes it, edits it, or lets the day roll into the next draft.
Sharable wishlists and cart previews
Released 20 July 2026 · from PRs #216, #217, #218, #219, #220
Added
- Wishlists can be shared with a public link. #216, #217
- The storefront header shows a live cart total. #218
- Saved carts show a thumbnail preview. #219 · screenshot
- Saved carts keep their thumbnail after a re-save. #220 · screenshot from the PR's passing run
Fixed
- Plural search terms return the same products as their singular. #215
What the draft is made from.
- Merged PRs of the day, their titles, bodies and the platform's own test-results comment, which carries a marker block the generator reads.
- Screenshots only from passing checks. A shot taken under a BLOCKED test block is withheld; the publish gate shows what it offers and what it holds back.
- Two bullets that say the same thing collapse to one with both PR references, so a punctuation difference never makes a duplicate line.
- Security fixes are generalised, never described in a way that points at the hole.
- Your instructions. The generation prompt is visible and editable per project, and every release records which instructions produced it.
The gate, and what is behind it.
A draft sits under "Awaiting review" until someone publishes it. Edit a release and a discard preview shows exactly what you would lose, so an edit never drops a citation or a screenshot silently. A project that wants continuous publishing can waive the gate. Publishing can send the release to Slack or any webhook, and any past release can be sent again by hand.
Everything is available to your own product through a versioned, incremental, read-only export API, with a releases-only key scope so a consumer can be handed the changelog and nothing else.
Where it stops today
- A release is cut per day, versioned by date and counter. There is no notion of a marketing version number unless you edit the title.
- Bullets are generated prose from PR metadata; a PR with a one-word title produces a thin bullet. The instructions field is the lever.
- Screenshots come from the platform's own run comments on the PR. A PR the platform did not test contributes text only.
- Publishing to Slack sends the release once; editing afterwards does not update the message.