Improve the base URI behavior when resolving a $ref to a resolution URI
which is different from the resolved schema's declared $id.
Accessing jsonschema.draftN_format_checker is deprecated. Instead, if you
want access to the format checker itself, it is exposed as
jsonschema.validators.DraftNValidator.FORMAT_CHECKER on any
jsonschema.protocols.Validator.
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.
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
Improve the base URI behavior when resolving a $ref to a resolution URI
which is different from the resolved schema's declared $id.
Accessing jsonschema.draftN_format_checker is deprecated. Instead, if you
want access to the format checker itself, it is exposed as
jsonschema.validators.DraftNValidator.FORMAT_CHECKER on any
jsonschema.protocols.Validator.
v4.15.0
A specific API Reference page is now present in the documentation.
$ref on 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_checks is deprecated. Use FormatChecker.checks on
an instance of FormatChecker instead.
unevaluatedItems has 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.Validator
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
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)
Bumps jsonschema from 4.8.0 to 4.16.0.
Release notes
Sourced from jsonschema's releases.
... (truncated)
Changelog
Sourced from jsonschema's changelog.
... (truncated)
Commits
ee024ff
Deprecate jsonschema.draftN_format_checker attributes.bd4306a
v4.16.0 -> CHANGELOGd9e093d
Fix more $ref cases when the lookup URL is different from an $id8cec498
Merge commit 'f5f839a5995c8005373214271989daae3537d70e'f5f839a
Squashed 'json/' changes from 6eaf7dff4..ed0b855e705b1860
Remove some now-unnecessary path mangling in doc builds.65802a7
Squashed 'json/' changes from 4cfead7ba..6eaf7dff42f15a98
Merge commit '65802a7ebcd0b661c829307354ab0c24e1e05031'575e786
Enable OpenGraph and copy buttons for the docs.420fc6b
Minor verbiage tweak for protocols.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)