Jsonschema

Latest version: v4.22.0

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

Scan your dependencies

Page 19 of 24

0.14.2

------

- Update vendored schemas: renovate, github-workflows, gitlab-ci (2022-03-30)
- Fix the vendored schema for GitLab to pull from the correct location.
Thanks :user:`dsch` for the fix!

0.14.1

------

- Update vendored schemas: azure-pipelines, renovate (2022-03-17)
- Allow invocation via ``python -m check_jsonschema``

0.14.0

------

- Drop support for python3.6 and improve internal type annotations
- Update vendored schemas (2022-02-28)
- Improve handling of file-URI inputs on Windows
- Add support for a new hook, ``check-metaschema``, which invokes
``check-jsonschema --check-metaschema``
- The ``check-jsonschema`` repo has moved to a new home at
https://github.com/python-jsonschema/check-jsonschema

0.13.0

------

- Add support for ``--check-metaschema``, which validates each instance file as a
JSON Schema, using the metaschema specified by ``"$schema"``
- ``--builtin-schema`` now validates its arguments (with ``choices=...``), and its
options are automatically picked up from the internal schema catalog and
listed in the ``--help`` output

0.12.0

------

- Add support for JSON5 files when ``pyjson5`` or ``json5`` is installed, and
update the Renovate hook to list JSON5 config files. If a JSON5 file is
checked without one of the necessary packages installed, a special error
with installation instructions will be raised
- Add hooks for GitLab CI and Bamboo Specs
- Remove the ``--failover-builtin-schema`` behavior. Now that vendored schemas
are used by default for hooks, this option had very limited utility.
- Update vendored schemas (2022-02-16)

0.11.0

------

- Add support for ``--data-transform azure-pipelines`` to handle compile-time
expressions in Pipelines files. This option is applied to the azure
pipelines hook (:issue:`29`)
- Improve handing of validation errors from schemas with ``anyOf`` and ``oneOf``
clauses. Show the "best match" from underlying errors, and add an option
``--show-all-validation-errors`` which displays all of the underlying errors
- Use vendored schemas in all hooks, not latest schemastore copies. This
ensures that hook behavior is consistent
(:issue:`38`)
- Update vendored schemas (2022-02-12)
- Use ``requests`` to make HTTP requests, and retry request failures

Page 19 of 24

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.