releases

Import Historical Release

Backfill the note for a bundle this install SKIPPED (TOS-4055).

Separate from /import on purpose. That endpoint requires the note to match the running bundle exactly, which is correct for the release you just adopted and is precisely what makes catch-up impossible: every skipped bundle is by definition not the one running, so every one of them 409s.

The guard here is the other half of the same idea, and it is deliberately one-directional: a note may be older than what this install runs, never newer. Backfilling history is safe; recording a release you have not actually reached would let What's New advertise code that is not deployed. Bundle versions are YYYYMMDD.HHMM-<sha>, so the timestamp prefix orders lexicographically and a plain string comparison is a date comparison.

post/api/internal/releases/import-historical

Request

  • Base URL: https://app.thinqos.com (the document declares no server; this is the origin it was published from)
  • URL: https://app.thinqos.com/api/internal/releases/import-historical
  • Auth: none declared

Headers

authorizationstring nullable

Request body

schema_version1
release_idstring uuid required
bundle_versionstring required
git_shastring required
source'backend' | 'web' | 'bridge' | 'docs' | 'full_stack'
category'feature' | 'improvement' | 'fix' | 'performance' | 'security' | 'integration' | 'admin' | 'internal' required
titlestring required
summarystring required
notes_markdownstring
notes_markdown_adminstring
notify_usersboolean required
published_atstring date-time required
generated_by_aiboolean

Response

Successful Response

storedboolean required
release_idstring uuid required
bundle_versionstring required

Changes

No recorded changes to this operation across all 1 revision of this API.