Bump jsonschema from 3.2.0 to 4.15.0
Bumps jsonschema from 3.2.0 to 4.15.0.
Release notes
Sourced from jsonschema's releases.
v4.15.0
What's Changed
- Enable dedicated API documentation page(s) by
@Julianin python-jsonschema/jsonschema#989Full Changelog: https://github.com/python-jsonschema/jsonschema/compare/v4.14.0...v4.15.0
v4.14.0
Full Changelog: https://github.com/python-jsonschema/jsonschema/compare/v4.13.0...v4.14.0
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
@hynekin python-jsonschema/jsonschema#987Full 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
@hynekin python-jsonschema/jsonschema#983Full 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_errorswhich 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
... (truncated)
Changelog
Sourced from jsonschema's changelog.
v4.15.0
- A specific API Reference page is now present in the documentation.
$refon earlier drafts (specifically draft 7 and 6) has been "fixed" to follow the specified behavior when present alongside a sibling$id. Specifically the ID is now properly ignored, and references are resolved against whatever resolution scope was previously relevant.v4.14.0
FormatChecker.cls_checksis deprecated. UseFormatChecker.checkson an instance ofFormatCheckerinstead.unevaluatedItemshas been fixed for draft 2019. It's nonetheless discouraged to use draft 2019 for any schemas, new or old.- Fix a number of minor annotation issues in
protocols.Validatorv4.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
... (truncated)
Commits
420fc6bMinor verbiage tweak for protocols.8ce8250Don't show type checker functions in TypeChecker reprs.6533d32Tweak the colorscheme for code blocks in docs.792311dSpelling...d67deccAdd some deprecated directives (for previous deprecations) to the docs.ca96760Make the link to Understanding JSON Schema more prominent.57b604eRemove the doc page for references.6d04fd7Remove the incorrect Optional from FormatChecker's formats annotation.fd491f9Minor non-functional changes to FormatChecker docstrings and init.a513c99Add a note to the CHANGELOG about #988.- 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 rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)