GET /releases/{regime}/{tag}/diff.json
The release’s own diff manifest, byte for byte as it shipped.
GET /releases/{regime}/{tag}/diff.jsonServes regimes/<regime>/releases/<tag>/<tag>.diff.json unchanged. This is why a feed item’s link is a link: following one lands on the manifest the entry was read out of, at the change, rather than on a page about it.
The bytes are the release plane’s and this service alters none of them, so the document’s shape is the manifest’s own — described here only as far as a client needs to find its way around it.
Authentication
Section titled “Authentication”No authentication requirement is stated for this operation.
Parameters
Section titled “Parameters”| Parameter | |
|---|---|
regime | The regime id, as the release directory spells it. (in path, required) |
tag | The release tag, as the release directory spells it. (in path, required) |
Responses
Section titled “Responses”The manifest as the release shipped it.
application/json — DiffManifest
that release has not been published to this service, or its manifest is not where the publication recorded it. It is 400 rather than 404 because the path is one this service routes and the release named in it is the part that is wrong
application/json — Error
Rendered from openregs/openregs@f3a2d10:docs/reference/feed-openapi.json