Bump jsonschema from 4.5.1 to 4.13.0

[dependabot[bot]]

Bumps jsonschema from 4.5.1 to 4.13.0.

Release notes

Sourced from jsonschema's releases.

v4.13.0

Full Changelog: https://github.com/python-jsonschema/jsonschema/compare/v4.12.1...v4.13.0

v4.12.1

What's Changed

• Use rST markers in README by @​hynek in python-jsonschema/jsonschema#987

Full Changelog: https://github.com/python-jsonschema/jsonschema/compare/v4.12.0...v4.12.1

v4.12.0

Full Changelog: https://github.com/python-jsonschema/jsonschema/compare/v4.11.0...v4.12.0

v4.11.0

What's Changed

• jsonschema deserves a ✨fancy✨ readme by @​hynek in python-jsonschema/jsonschema#983

Full Changelog: https://github.com/python-jsonschema/jsonschema/compare/v4.10.3...v4.11.0

v4.10.3

Full Changelog: https://github.com/python-jsonschema/jsonschema/compare/v4.10.2...v4.10.3

v4.10.2

• Fix a second place where subclasses may have added attrs attributes (#982).

Full Changelog: https://github.com/python-jsonschema/jsonschema/compare/v4.10.1...v4.10.2

v4.10.1

• 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: https://github.com/python-jsonschema/jsonschema/compare/v4.10.0...v4.10.1

v4.10.0

• Add support for referencing schemas with $ref across different versions of the specification than the referrer's

Full Changelog: https://github.com/python-jsonschema/jsonschema/compare/v4.9.1...v4.10.0

v4.9.1

• Update some documentation examples to use newer validator releases in their sample code.

... (truncated)

Changelog

Sourced from jsonschema's changelog.

v4.13.0

• 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.

v4.12.1

• Fix some stray comments in the README.

v4.12.0

• 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.

v4.11.0

• Make the rendered README in PyPI simpler and fancier. Thanks Hynek (#983)!

v4.10.3

• jsonschema.validators.validator_for now properly uses the explicitly provided default validator even if the $schema URI is not found.

v4.10.2

• Fix a second place where subclasses may have added attrs attributes (#982).

v4.10.1

• 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

... (truncated)

Commits

• a60a087 Support validator classes whose metaschema uses a different dialect.
• edaf2a1 Remove some old unnecessary explicit object superclasses.
• dfd41e8 Update the CHANGELOG.
• 345ffb1 Merge pull request #987 from hynek/fix-markers
• 1d05e4d Use rST markers in README
• e69cb7a Warn at runtime when subclassing validator classes.
• 549f9e5 Fix the rest of the CHANGELOG headings from #983.
• 90f7d20 Merge pull request #983 from hynek/fancy-sparkles
• 837bd09 Cut the middle part
• 990bae7 Use an explicit default provided to validator_for in all cases.
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)