internal
release-notes
Roll Up Week
post/api/v1/internal/release-notes/roll-up
Request body
week_startstring date required
Response
Successful Response
outcome'created' | 'merged' | 'merged_into_open_digest' | 'merged_into_published' | 'merged_after_digest' | 'no_changes' required
What one week roll-up run did.
NO_CHANGES is a first-class outcome rather than an empty duplicate draft — a re-run with nothing new must say so, not mint one.
A week holds one entry, so every merge outcome names what the merge touched. MERGED_INTO_PUBLISHED is separate from MERGED because the entry it grew is already in front of customers: the operator is editing live copy, not a draft, and nothing else on the response says so.
MERGED_INTO_OPEN_DIGEST asks staff to reroll the editable email. MERGED_AFTER_DIGEST warns that an earlier sent email claimed the week, so later bullets need an explicit repeat.
releases_addedinteger required