debian-forge/schemas
David Rheinsberg 376cbffd13 schemas/osbuild2: mark version as required
The v2 manifest requires the `version` key to be present to be
distinguishable from v1. While technically the manifest can be used
standalong without a `version` key, it does prevent us implementing the
manifest correctly in osbuild (i.e., we are unable to process a v2
manifest without the `version` key, because we are unable to autodetect
it then).

Mark the key as required. It does kind of break backwards compatibility
of the schema, but at the same time we always treated it this way,
anyway. So this should be fine.

Signed-off-by: David Rheinsberg <david.rheinsberg@gmail.com>
2022-07-25 16:01:48 +02:00
..
osbuild1.json schema/osbuild1.json: convert to draft4 standard 2020-05-12 22:00:38 +02:00
osbuild2.json schemas/osbuild2: mark version as required 2022-07-25 16:01:48 +02:00