Martin Vrachev 99a4d71b72 Update supported specification version to 1.0.28 ... I looked into all changes between our current version 1.0.19 and the current version of the specification 1.0.28 and I agree with Jussi that the only one not fully resolved is: "8dafd00 (tag: v1.0.24) Clarify optional attributes" and more precisely the changes from commit: 4dd279bc31 It doesn't make sense to have a target file without "paths" or "path_hash_prefixes", so our `python-tuf requirement to have at least one of them set makes sense. Both with Jussi we agreed that we can easily loosen this requirement if when solving https://github.com/theupdateframework/specification/issues/200 it's decided that both of them can be omitted, but for now, we decided it's better to stick to our current requirement to have one of them set. Signed-off-by: Martin Vrachev <mvrachev@vmware.com>		2022-02-04 15:38:34 +02:00
..
serialization	Make (De)SerializationError a RepositoryError	2022-01-19 16:52:19 +02:00
__init__.py	tuf/api: Expose tuf.api as a package	2020-10-15 14:35:14 +01:00
exceptions.py	exceptions: rename FetcherHTTPError	2022-02-04 11:03:12 +02:00
metadata.py	Update supported specification version to 1.0.28	2022-02-04 15:38:34 +02:00