English
Changelog
Changelog body lives only on GET .../changelog/{channel}/{os}/{arch}. Check JSON has no changelog.
When to use
Use when the client UI shows a version range. Store protocols still project Version changelog into their document (for example Sparkle <description>).
Configuration entry
Project Settings → Changelog Defaults (scope, layout, counts). Click-path: Settings. Instance ceilings: changelog.default_entries / max_entries in config.yaml. YAML default > max refuses to listen.
Rules and error codes
| Condition | HTTP | Code |
|---|---|---|
Bad scope/layout or illegal from_version | 400 | CHANGELOG_QUERY_INVALIDIllegal changelog query |
| Unknown path channel | 400 | INVALID_QUERY_PARAMIllegal query (including announcement version and unknown changelog channel) |
| Channel token mismatch | 404 | NOT_FOUNDGeneric missing resource |
| Unknown from/to version | 404 | VERSION_NOT_FOUNDVersion missing |
| Project counts above instance ceiling | 400 | INVALID_REQUESTIllegal body/fields (including non-.mmdb, caps, unknown matrix pair, duplicate listing) |
No from_version returns the newest default_entries (product default 5). With from, truncate to max_entries (default 50); overflow stays 200. Markdown ${site_url} expands from RequestOrigin.
Client duties
GET changelog after check if you need the body. Do not put changelog query params on check.
Related: Changelog API.