Sign in
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

Changes

Changed in 2 of the 30 revisions of this API.3

  • 499d0b94aa941See the full diff
    • ●

      added the new merged_into_open_digest enum value to the response property for the response status

      response-property-enum-value-added

  • ba2b8d9621612See the full diff
    • ●

      added the new merged_after_digest enum value to the response property for the response status

      response-property-enum-value-added

    • ●

      added the new merged_into_published enum value to the response property for the response status

      response-property-enum-value-added

    This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog