pixi icon indicating copy to clipboard operation
pixi copied to clipboard

Published 20 hours ago • verified publisher icon prefix-dev

chore(ci): Update Pixi (major)

Open renovate[bot] opened this issue 1 month ago • 1 comments

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.4,<3
pillow (source) feature-docs major >=11.3.0,<12 -> >=12,<13
pytest (source) feature-pytest major >=8.4.2,<9 -> >=9.0.1,<10

[!WARNING] Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

python-jsonschema/jsonschema (jsonschema)

v4.25.1

=======

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

v4.25.0

=======

  • 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

=======

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

v4.24.0

=======

  • 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

=======

  • 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

=======

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

v4.21.0

=======

  • 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

=======

  • 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

=======

  • 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

=======

  • 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

=======

  • 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

=======

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

v4.18.3

=======

  • 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

=======

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

v4.18.1

=======

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

v4.18.0

=======

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.4

Compare Source

  • fix: glob_matcher jsonschema values
  • feat: add optional standard glob matcher (doublestar) (#​1188) by @​jasonwbarnett

v2.0.3

Compare Source

v2.0.2

Compare Source

  • fix: add mutex lock before all git commands (#​1178) by @​mrexox

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

pytest-dev/pytest (pytest)

v9.0.1

Compare Source

pytest 9.0.1 (2025-11-12)

Bug fixes

  • #​13895: Restore support for skipping tests via raise unittest.SkipTest.
  • #​13896: The terminal progress plugin added in pytest 9.0 is now automatically disabled when iTerm2 is detected, it generated desktop notifications instead of the desired functionality.
  • #​13904: Fixed the TOML type of the verbosity settings in the API reference from number to string.
  • #​13910: Fixed UserWarning: Do not expect file_or_dir on some earlier Python 3.12 and 3.13 point versions.

Packaging updates and notes for downstreams

  • #​13933: The tox configuration has been adjusted to make sure the desired version string can be passed into its package_env through the SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST environment variable as a part of the release process -- by webknjaz.

Contributor-facing changes

  • #​13891, #​13942: The CI/CD part of the release automation is now capable of creating GitHub Releases without having a Git checkout on disk -- by bluetech and webknjaz.
  • #​13933: The tox configuration has been adjusted to make sure the desired version string can be passed into its package_env through the SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST environment variable as a part of the release process -- by webknjaz.

v9.0.0

Compare Source

pytest 9.0.0 (2025-11-05)

New features

  • #​1367: Support for subtests has been added.

    subtests <subtests> are an alternative to parametrization, useful in situations where the parametrization values are not all known at collection time.

    Example:

    def contains_docstring(p: Path) -> bool:
    """Return True if the given Python file contains a top-level docstring."""
    ...

def test_py_files_contain_docstring(subtests: pytest.Subtests) -> None:
    for path in Path.cwd().glob("*.py"):
        with subtests.test(path=str(path)):
            assert contains_docstring(path)

    Each assert failure or error is caught by the context manager and reported individually, giving a clear picture of all files that are missing a docstring.

    In addition, unittest.TestCase.subTest is now also supported.

    This feature was originally implemented as a separate plugin in pytest-subtests, but since then has been merged into the core.

    [!NOTE] This feature is experimental and will likely evolve in future releases. By that we mean that we might change how subtests are reported on failure, but the functionality and how to use it are stable.

  • #​13743: Added support for native TOML configuration files.

    While pytest, since version 6, supports configuration in pyproject.toml files under [tool.pytest.ini_options], it does so in an "INI compatibility mode", where all configuration values are treated as strings or list of strings. Now, pytest supports the native TOML data model.

    In pyproject.toml, the native TOML configuration is under the [tool.pytest] table.

    # pyproject.toml
[tool.pytest]
minversion = "9.0"
addopts = ["-ra", "-q"]
testpaths = [
    "tests",
    "integration",
]

    The [tool.pytest.ini_options] table remains supported, but both tables cannot be used at the same time.

    If you prefer to use a separate configuration file, or don't use pyproject.toml, you can use pytest.toml or .pytest.toml:

    # pytest.toml or .pytest.toml
[pytest]
minversion = "9.0"
addopts = ["-ra", "-q"]
testpaths = [
    "tests",
    "integration",
]

    The documentation now (sometimes) shows configuration snippets in both TOML and INI formats, in a tabbed interface.

    See config file formats for full details.

  • #​13823: Added a "strict mode" enabled by the strict configuration option.

    When set to true, the strict option currently enables

    • strict_config
    • strict_markers
    • strict_parametrization_ids
    • strict_xfail

    The individual strictness options can be explicitly set to override the global strict setting.

    The previously-deprecated --strict command-line flag now enables strict mode.

    If pytest adds new strictness options in the future, they will also be enabled in strict mode. Therefore, you should only enable strict mode if you use a pinned/locked version of pytest, or if you want to proactively adopt new strictness options as they are added.

    See strict mode for more details.

  • #​13737: Added the strict_parametrization_ids configuration option.

    When set, pytest emits an error if it detects non-unique parameter set IDs, rather than automatically making the IDs unique by adding 0, 1, ... to them. This can be particularly useful for catching unintended duplicates.

  • #​13072: Added support for displaying test session progress in the terminal tab using the OSC 9;4; ANSI sequence. When pytest runs in a supported terminal emulator like ConEmu, Gnome Terminal, Ptyxis, Windows Terminal, Kitty or Ghostty, you'll see the progress in the terminal tab or window, allowing you to monitor pytest's progress at a glance.

    This feature is automatically enabled when running in a TTY. It is implemented as an internal plugin. If needed, it can be disabled as follows:

    • On a user level, using -p no:terminalprogress on the command line or via an environment variable PYTEST_ADDOPTS='-p no:terminalprogress'.
    • On a project configuration level, using addopts = "-p no:terminalprogress".

  • #​478: Support PEP420 (implicit namespace packages) as --pyargs target when consider_namespace_packages is true in the config.

    Previously, this option only impacted package imports, now it also impacts tests discovery.

  • #​13678: Added a new faulthandler_exit_on_timeout configuration option set to "false" by default to let faulthandler interrupt the pytest process after a timeout in case of deadlock.

    Previously, a faulthandler timeout would only dump the traceback of all threads to stderr, but would not interrupt the pytest process.

    -- by ogrisel.

  • #​13829: Added support for configuration option aliases via the aliases parameter in Parser.addini() <pytest.Parser.addini>.

    Plugins can now register alternative names for configuration options, allowing for more flexibility in configuration naming and supporting backward compatibility when renaming options. The canonical name always takes precedence if both the canonical name and an alias are specified in the configuration file.

Improvements in existing functionality

  • #​13330: Having pytest configuration spread over more than one file (for example having both a pytest.ini file and pyproject.toml with a [tool.pytest.ini_options] table) will now print a warning to make it clearer to the user that only one of them is actually used.

    -- by sgaist

  • #​13574: The single argument --version no longer loads the entire plugin infrastructure, making it faster and more reliable when displaying only the pytest version.

    Passing --version twice (e.g., pytest --version --version) retains the original behavior, showing both the pytest version and plugin information.

    [!NOTE] Since --version is now processed early, it only takes effect when passed directly via the command line. It will not work if set through other mechanisms, such as PYTEST_ADDOPTS or addopts.

  • #​13823: Added strict_xfail as an alias to the xfail_strict option, strict_config as an alias to the --strict-config flag, and strict_markers as an alias to the --strict-markers flag. This makes all strictness options consistently have configuration options with the prefix strict_.

  • #​13700: --junitxml no longer prints the generated xml file summary at the end of the pytest session when --quiet is given.

  • #​13732: Previously, when filtering warnings, pytest would fail if the filter referenced a class that could not be imported. Now, this only outputs a message indicating the problem.

  • #​13859: Clarify the error message for pytest.raises() when a regex match fails.

  • #​13861: Better sentence structure in a test's expected error message. Previously, the error message would be "expected exception must be <expected>, but got <actual>". Now, it is "Expected <expected>, but got <actual>".

Removals and backward incompatible breaking changes

  • #​12083: Fixed a bug where an invocation such as pytest a/ a/b would cause only tests from a/b to run, and not other tests under a/.

    The fix entails a few breaking changes to how such overlapping arguments and duplicates are handled:

    1. <span class="title

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[bot] avatar Oct 28 '25 05:10 renovate[bot]

⚠️ 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-
  │ 64'
  ├─▶   × 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[bot] avatar Oct 28 '25 05:10 renovate[bot]