summaryrefslogtreecommitdiff
path: root/doc/json-hooks-protocol.md
Commit message (Collapse)AuthorAgeFilesLines
* Fix a typo in json-hooks-protocol.mdBrian Murray2021-04-281-1/+1
|
* doc: Single-line JSON encoding is still mandatoryJulian Andres Klode2021-04-231-2/+2
| | | | Gbp-Dch: ignore
* json: Hook protocol 0.2 (added upgrade,downgrade,reinstall modes)Julian Andres Klode2021-04-231-17/+31
| | | | | | | | | Hook protocol 0.2 makes the new fields we added mandatory, and replaces `install` mode with `upgrade`, `downgrade`, `reinstall` where appropriate. Hook negotiation is hacky, but it's the best we can do for now. Users are advised to upgrade to 0.2
* json: Add `package-list` and `statistics` install hooksJulian Andres Klode2021-04-231-1/+7
| | | | This enables hooks to output additional information.
* json: Add origins fields to versionJulian Andres Klode2021-04-231-0/+10
| | | | | | Provide access to the origins of a package, such that tools can display information about them; for example, you can write a hook counting security upgrades.
* Perform minor copy-editing on the docsMartin Michlmayr2019-04-041-1/+1
|
* json-hooks-protocol: The "pin" field is optionalJulian Andres Klode2019-02-071-1/+1
|
* move special READMEs into doc/ and format as mdDavid Kalnischkies2018-05-051-0/+159
The formatting is very basic and more should probably be done, but we at least get the files out of the root directory which in case of the various READMEs was confusing salsa which one display as (central) README.