Jsonschema

Latest version: v4.22.0

Safety actively analyzes 629855 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 21 of 24

0.8.1

-----

- Bugfix for package metadata to include builtin schemas

0.8.0

-----

- ``check-jsonschema`` now ships with vendored versions of the external schemas
used for the default suite of hooks. The vendored schemas are used as a
failover option in the event that downloading an external schema fails. This
resolves :issue:`21`
- New CLI options, ``--builtin-schema`` and ``--failover-builtin-schema`` are
available to access the builtin schemas. See documentation for details.
- Use the latest version (version 4) of the ``jsonschema`` library. Note
that ``jsonschema`` has dropped support for python3.6, and ``check-jsonschema``
will therefore use ``jsonschema`` version 3 when running on python3.6
- The path shown in error messages is now a valid
`JSONPath <https://goessner.net/articles/JsonPath/>`_ expression

0.7.1

-----

- Bugfix: validation errors were not being displayed correctly.
- Errors are now sent to stderr instead of stdout.

0.7

====

* Partial support for (JSON Pointer) ``$ref``
* Deprecations

* ``Validator`` is replaced by ``Draft3Validator`` with a slightly different
interface
* ``validator(meta_validate=False)``

0.7.0

-----

- Exception tracebacks for several known-cases are printed in a shortened
format. A new option, ``--traceback-mode`` can be used to request long traces,
as in ``--traceback-mode full``
- For schemas which do not include ``$id``, the schema URI will be used for
``$ref`` resolution. This applies to HTTP(S) schema URI as well as to local
paths. Thanks to :user:`dkolepp` for the bug report and contributions!

0.6

====

* Bugfixes

* Issue 30 - Wrong behavior for the dependencies property validation
* Fixed a miswritten test

Page 21 of 24

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.