v2021.10 Release:

- Fix working with json-schema 4.0.x release

- Ensure standard unit suffix properties don't have a $ref as they
  already have a type

- Improvements and fixes to items/maxItems/minItems meta-schemas and
  fixups

- Add a meta-schema to prefer enum over oneOf+const entries

- Add a 'chassis-type' property

- /chosen kexec documentation improvements

- Fix pciclass compatible string pattern

v2021.07 Release

- Fixes for compatibility with upcoming jsonschema 4.0 release

- Preparations for jsonschema draft2019-09 support

- Allow -microvolt properties to be a matrix

- Remove a YAML1.1 hack avoiding collision with 'on' string in DT
  property values treated as boolean

v2021.06 Release:

- Updates to simple-bus schema

- Ensure referenced schemas always apply to DT nodes

- Use GH Actions for CI and publishing

dtschema v2021.05

- Add extra warning message text from meta-schemas. This will give users
a better hint about how to fix warnings.

dtschema v2021.03:

- Exclude '.*-names' properties from vendor meta-schema

- Use base.yaml meta-schema for core schemas

- Work-around handling of signed types

- Apply meta-schema for properties with unit suffix

- Make meta-schema descend into allOf/anyOf/oneOf/if schemas

v2021.02.1 Release

- Add missing -kBps and -femtofarads unit suffixes

v2021.02 Release:

- Stricter root node and simple-bus unit-address checks

- Better undocumented compatible string checking

- Rework fixups yet again. Now all fixups are done in one spot (after
  check_schema()). Matching of unit suffixes is added for integer
  fixups.

- Make assigned-clocks* properties always allowed.

- Add percentage as unit suffix

- Add meta-schemas for hwlock and nvmem bindings

dtschema v2021.01

- Various meta-schema improvements

dtschema v2020.12:

- Add graph schema

- Add IIO schemas

- Allow draft2019.09 $def keyword

- Fix warning filtering on disabled child nodes

- Drop 'allOf' for $ref (draft2019.09 syntax)

dtschema: Don't print duplicate error messages

Sometimes we may have duplicate error messages printed. They aren't
really duplicates as they are the same schema check, but from different
subschemas in an oneOf/anyOf. In any case, there's not any more useful
information, so let's drop the message.

Signed-off-by: Rob Herring <[email protected]>