Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 28, 2025

This PR contains the following updates:

Package Type Update Change
jsonschema feature-schema major >=3.2.0,<4 -> >=4.25.1,<5
lefthook feature-lint major >=1.13.6,<2 -> >=2.0.2,<3
pillow (source) feature-docs major >=11.3.0,<12 -> >=12,<13

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

python-jsonschema/jsonschema (jsonschema)

v4.25.1

Compare Source

=======

  • Fix an incorrect required argument in the Validator protocol's type annotations (#​1396).

v4.25.0

Compare Source

=======

  • Add support for the iri and iri-reference formats to the format-nongpl extra via the MIT-licensed rfc3987-syntax.
    They were alread supported by the format extra. (#​1388).

v4.24.1

Compare Source

=======

  • Properly escape segments in ValidationError.json_path (#​139).

v4.24.0

Compare Source

=======

  • Fix improper handling of unevaluatedProperties in the presence of additionalProperties (#​1351).
  • Support for Python 3.8 has been dropped, as it is end-of-life.

v4.23.0

Compare Source

=======

  • Do not reorder dictionaries (schemas, instances) that are printed as part of validation errors.
  • Declare support for Py3.13

v4.22.0

Compare Source

=======

  • Improve best_match (and thereby error messages from jsonschema.validate) in cases where there are multiple sibling errors from applying anyOf / allOf -- i.e. when multiple elements of a JSON array have errors, we now do prefer showing errors from earlier elements rather than simply showing an error for the full array (#​1250).
  • (Micro-)optimize equality checks when comparing for JSON Schema equality by first checking for object identity, as == would.

v4.21.1

Compare Source

=======

  • Slightly speed up the contains keyword by removing some unnecessary validator (re-)creation.

v4.21.0

Compare Source

=======

  • Fix the behavior of enum in the presence of 0 or 1 to properly consider True and False unequal (#​1208).
  • Special case the error message for {min,max}{Items,Length,Properties} when they're checking for emptiness rather than true length.

v4.20.0

Compare Source

=======

  • Properly consider items (and properties) to be evaluated by unevaluatedItems (resp. unevaluatedProperties) when behind a $dynamicRef as specified by the 2020 and 2019 specifications.
  • jsonschema.exceptions.ErrorTree.__setitem__ is now deprecated.
    More broadly, in general users of jsonschema should never be mutating objects owned by the library.

v4.19.2

Compare Source

=======

  • Fix the error message for additional items when used with heterogeneous arrays.
  • Don't leak the additionalItems keyword into JSON Schema draft 2020-12, where it was replaced by items.

v4.19.1

Compare Source

=======

  • Single label hostnames are now properly considered valid according to the hostname format.
    This is the behavior specified by the relevant RFC (1123).
    IDN hostname behavior was already correct.

v4.19.0

Compare Source

=======

  • Importing the Validator protocol directly from the package root is deprecated.
    Import it from jsonschema.protocols.Validator instead.
  • Automatic retrieval of remote references (which is still deprecated) now properly succeeds even if the retrieved resource does not declare which version of JSON Schema it uses.
    Such resources are assumed to be 2020-12 schemas.
    This more closely matches the pre-referencing library behavior.

v4.18.6

=======

  • Set a jsonschema specific user agent when automatically retrieving remote references (which is deprecated).

v4.18.4

Compare Source

=======

  • Improve the hashability of wrapped referencing exceptions when they contain hashable data.

v4.18.3

Compare Source

=======

  • Properly preserve applicable_validators in extended validators.
    Specifically, validators extending early drafts where siblings of $ref were ignored will properly ignore siblings in the extended validator.

v4.18.2

Compare Source

=======

  • Fix an additional regression with the deprecated jsonschema.RefResolver and pointer resolution.

v4.18.1

Compare Source

=======

  • Fix a regression with jsonschema.RefResolver based resolution when used in combination with a custom validation dialect (via jsonschema.validators.create).

v4.18.0

Compare Source

=======

This release majorly rehauls the way in which JSON Schema reference resolution is configured.
It does so in a way that should be backwards compatible, preserving old behavior whilst emitting deprecation warnings.

  • jsonschema.RefResolver is now deprecated in favor of the new referencing library <https://github.com/python-jsonschema/referencing/>_.
    referencing will begin in beta, but already is more compliant than the existing $ref support.
    This change is a culmination of a meaningful chunk of work to make $ref resolution more flexible and more correct.
    Backwards compatibility should be preserved for existing code which uses RefResolver, though doing so is again now deprecated, and all such use cases should be doable using the new APIs.
    Please file issues on the referencing tracker if there is functionality missing from it, or here on the jsonschema issue tracker if you have issues with existing code not functioning the same, or with figuring out how to change it to use referencing.
    In particular, this referencing change includes a change concerning automatic retrieval of remote references (retrieving http://foo/bar automatically within a schema).
    This behavior has always been a potential security risk and counter to the recommendations of the JSON Schema specifications; it has survived this long essentially only for backwards compatibility reasons, and now explicitly produces warnings.
    The referencing library itself will not automatically retrieve references if you interact directly with it, so the deprecated behavior is only triggered if you fully rely on the default $ref resolution behavior and also include remote references in your schema, which will still be retrieved during the deprecation period (after which they will become an error).
  • Support for Python 3.7 has been dropped, as it is nearing end-of-life.
    This should not be a "visible" change in the sense that requires-python has been updated, so users using 3.7 should still receive v4.17.3 when installing the library.
  • On draft 2019-09, unevaluatedItems now properly does not consider items to be evaluated by an additionalItems schema if items is missing from the schema, as the specification says in this case that additionalItems must be completely ignored.
  • Fix the date format checker on Python 3.11 (when format assertion behavior is enabled), where it was too liberal (#​1076).
  • Speed up validation of unevaluatedProperties (#​1075).

Deprecations

  • jsonschema.RefResolver -- see above for details on the replacement
  • jsonschema.RefResolutionError -- see above for details on the replacement
  • relying on automatic resolution of remote references -- see above for details on the replacement
  • importing jsonschema.ErrorTree -- instead import it via jsonschema.exceptions.ErrorTree
  • importing jsonschema.FormatError -- instead import it via jsonschema.exceptions.FormatError

v4.17.3

=======

  • Fix instantiating validators with cached refs to boolean schemas
    rather than objects (#​1018).

v4.17.1

=======

  • The error message when using unevaluatedProperties with a non-trivial
    schema value (i.e. something other than false) has been improved (#​996).

v4.17.0

=======

  • The check_schema method on jsonschema.protocols.Validator instances
    now enables format validation by default when run. This can catch some
    additional invalid schemas (e.g. containing invalid regular expressions)
    where the issue is indeed uncovered by validating against the metaschema
    with format validation enabled as an assertion.
  • The jsonschema CLI (along with jsonschema.cli the module) are now
    deprecated. Use check-jsonschema instead, which can be installed via
    pip install check-jsonschema and found
    here <https://github.com/python-jsonschema/check-jsonschema>_.

v4.16.0

=======

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

======

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

v4.9.0

======

  • Fix relative $ref resolution when the base URI is a URN or other scheme
    (#​544).
  • pkgutil.resolve_name is now used to retrieve validators
    provided on the command line. This function is only available on
    3.9+, so 3.7 and 3.8 (which are still supported) now rely on the
    pkgutil_resolve_name <https://pypi.org/project/pkgutil_resolve_name/>_
    backport package. Note however that the CLI itself is due
    to be deprecated shortly in favor of check-jsonschema <https://github.com/python-jsonschema/check-jsonschema>_.

v4.8.0

======

  • best_match no longer traverses into anyOf and oneOf when all of
    the errors within them seem equally applicable. This should lead to clearer
    error messages in some cases where no branches were matched.

v4.7.2

======

  • Also have best_match handle cases where the type validator is an
    array.

v4.7.1

======

  • Minor tweak of the PyPI hyperlink names

v4.6.2

======

  • Fix a number of minor typos in docstrings, mostly private ones (#​969)

v4.6.1

======

  • Gut the (incomplete) implementation of recursiveRef on draft 2019. It
    needs completing, but for now can lead to recursion errors (e.g. #​847).

v4.6.0

======

  • Fix unevaluatedProperties and unevaluatedItems for types they should
    ignore (#​949)
  • jsonschema now uses hatch <https://hatch.pypa.io/>_ for its build
    process. This should be completely transparent to end-users (and only matters
    to contributors).

v4.5.1

======

  • Revert changes to $dynamicRef which caused a performance regression
    in v4.5.0

v4.4.0

======

  • Add mypy support (#​892)
  • Add support for Python 3.11

v4.3.3

======

  • Properly report deprecation warnings at the right stack level (#​899)

v4.3.2

======

  • Additional performance improvements for resolving refs (#​896)

v4.3.1

======

  • Resolving refs has had performance improvements (#​893)

v4.3.0

======

  • Fix undesired fallback to brute force container uniqueness check on
    certain input types (#​893)
  • Implement a PEP544 Protocol for validator classes (#​890)

v4.2.1

======

  • Pin importlib.resources from below (#​877)

v4.2.0

======

  • Use importlib.resources to load schemas (#​873)
  • Ensure all elements of arrays are verified for uniqueness by uniqueItems
    (#​866)

v4.1.2

======

  • Fix dependentSchemas to properly consider non-object instances to be
    valid (#​850)

v4.1.1

======

  • Fix prefixItems not indicating which item was invalid within the instance
    path (#​862)

v4.1.0

======

  • Add Python 3.10 to the list of supported Python versions

v4.0.1

======

  • Fix the declaration of minimum supported Python version (#​846)
evilmartians/lefthook (lefthook)

v2.0.2

Compare Source

v2.0.1

Changelog

python-pillow/Pillow (pillow)

v12.0.0

Compare Source

https://pillow.readthedocs.io/en/stable/releasenotes/12.0.0.html

Removals

Deprecations

Documentation

Dependencies

Testing

Type hints

Other changes


Configuration

📅 Schedule: Branch creation - "on tuesday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Oct 28, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pixi.lock
ExecError: Command failed: pixi lock --no-progress --color=never --quiet
Error:   × failed to solve requirements of environment 'default' for platform 'osx-
  │ arm64'
  ├─▶   × failed to solve the environment
  │   
  ╰─▶ Cannot solve the request because of: The following packages are
      incompatible
      ├─ jsonschema >=4.25.1,<5 can be installed with any of the following
      options:
      │  └─ jsonschema 4.25.1
      └─ cffconvert >=2.0.0,<3 cannot be installed because there are no viable
      options:
         └─ cffconvert 2.0.0 | 2.0.0 | 2.0.0 would require
            └─ jsonschema >=3.0,<4, which cannot be installed because there
      are no viable options:
               └─ jsonschema 3.2.0, which conflicts with the versions reported
      above.
      


@renovate renovate bot force-pushed the renovate/major-pixi branch from 2ba6666 to 98455da Compare October 28, 2025 14:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants