Skip to content

Releases: python-jsonschema/jsonschema

v4.13.0

19 Aug 12:31
Compare
Choose a tag to compare
  • Add support for creating validator classes whose metaschema uses a different
    dialect than its schemas. In other words, they may use draft2020-12 to define
    which schemas are valid, but the schemas themselves use draft7 (or a custom
    dialect, etc.) to define which instances are valid. Doing this is likely
    not something most users, even metaschema authors, may need, but occasionally
    will be useful for advanced use cases.

Full Changelog: v4.12.1...v4.13.0

v4.12.1

18 Aug 10:20
Compare
Choose a tag to compare

What's Changed

Full Changelog: v4.12.0...v4.12.1

v4.12.0

18 Aug 10:20
Compare
Choose a tag to compare
  • Warn at runtime when subclassing validator classes. Doing so was not
    intended to be public API, though it seems some downstream libraries
    do so. A future version will make this an error, as it is brittle and
    better served by composing validator objects instead. Feel free to reach
    out if there are any cases where changing existing code seems difficult
    and I can try to provide guidance.

Full Changelog: v4.11.0...v4.12.0

v4.11.0

18 Aug 09:22
Compare
Choose a tag to compare

What's Changed

  • jsonschema deserves a ✨fancy✨ readme by @hynek in #983

Full Changelog: v4.10.3...v4.11.0

v4.10.3

18 Aug 07:48
Compare
Choose a tag to compare
  • jsonschema.validators.validator_for now properly uses the explicitly
    provided default validator even if the $schema URI is not found.

Full Changelog: v4.10.2...v4.10.3

v4.10.2

17 Aug 16:15
Compare
Choose a tag to compare
  • Fix a second place where subclasses may have added attrs attributes (#982).

Full Changelog: v4.10.1...v4.10.2

v4.10.1

17 Aug 15:04
Compare
Choose a tag to compare
  • Fix Validator.evolve (and APIs like iter_errors which call it) for cases
    where the validator class has been subclassed. Doing so wasn't intended to be
    public API, but given it didn't warn or raise an error it's of course
    understandable. The next release however will make it warn (and a future one
    will make it error). If you need help migrating usage of inheriting from a
    validator class feel free to open a discussion and I'll try to give some
    guidance (#982).

Full Changelog: v4.10.0...v4.10.1

v4.10.0

16 Aug 09:51
Compare
Choose a tag to compare
  • Add support for referencing schemas with $ref across different versions
    of the specification than the referrer's

Full Changelog: v4.9.1...v4.10.0

v4.9.1

03 Aug 08:40
Compare
Choose a tag to compare
  • Update some documentation examples to use newer validator releases in their
    sample code.

Full Changelog: v4.9.0...v4.9.1

v4.9.0

31 Jul 07:27
Compare
Choose a tag to compare
  • Fix relative $ref resolution when the base URI is a URN or other scheme
    (#544).
  • pkgutil.resolve_name is now used to retrieve validators
    provided on the command line. This function is only available on
    3.9+, so 3.7 and 3.8 (which are still supported) now rely on the
    pkgutil_resolve_name <https://pypi.org/project/pkgutil_resolve_name/>_
    backport package. Note however that the CLI itself is due
    to be deprecated shortly in favor of check-jsonschema <https://github.com/python-jsonschema/check-jsonschema>_.

Full Changelog: v4.8.0...v4.9.0