Skip to content

build(deps): update development dependencies (major versions) (main) (major) - #289

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/main-major-dev-dependencies
Closed

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/main-major-dev-dependencies

Conversation

@renovate

@renovate renovate Bot commented Oct 31, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
pytest-check ~=2.3 → ~=3.0 age confidence
pytest-cov (changelog) ~=5.0 → ~=7.1 age confidence

Release Notes

okken/pytest-check (pytest-check)

v3.0.3

Compare Source

Fixed
  • Second attempt to fix issue #​210.
    • First attempt "seemed" fixed in the context of the in-process pytest runner, but failed as a subprocess.
    • I've added a subprocess run, and a fix.
    • Pretty sure it's fixed now.

v3.0.2

Compare Source

Fixed
  • Report failed checks correctly in unittest.IsolatedAsyncioTestCase tests (issue #​210).
Developer Experience
  • Split mypy checks into separate tox environments so they can run in parallel with tox -p.

v3.0.1

Compare Source

Fixed
  • Truncate long local values in check pseudo tracebacks with -l or -lv, while preserving full values with -lvv (issue #​208). Thanks Neallin-917

v3.0.0

Compare Source

Highlights
  • This plugin should now work fine with tests running in parallel with other plugins such as pytest-run-parallel, pytest-swarm, or pytest-freethreaded.
Migration Notes
  • Failures raised in helper threads remain part of their parent test's report. When reading check_log from a worker thread, its failure state is now independent of other concurrently running threads.
  • Thanks dpadninja for getting the ball rolling on this
Changed
  • Check failure state is now isolated per thread and aggregated through parent/child thread relationships, preserving a test's combined failure report when it starts helper threads.
Fixed
  • Prevent failure counts and messages from leaking between tests executed concurrently in threads.
  • Verify thread-state isolation with pytest-swarm, pytest-freethreaded, and pytest-run-parallel.

v2.10.1

Compare Source

Highlights
  • Fix call_on_fail() functionality, issue #​203
  • Fix an issue with -x and check.raises(), PR #​205
  • Show relative path in psuedo traceback
  • Test against 3.14t, 3.15, 3.15t
Changed
  • test against Python 3.14t, 3.15, and 3.15t
  • show relative path from log_failures with tb
    • this is to allow clicking on the file name in IDEs
    • thanks dpinol
Fixed
  • #​203 call_on_fail() no longer registers globally since 2.9.1
  • Issue with raises

v2.9.1

Compare Source

Fixed

v2.8.0

Compare Source

Added
  • Support Request #​122: Feature proposal: Capability to mark checks as xfail
  • Allow check helper functions, including raises(), to accept an xfail reason. A failing check can now produce an xfailed test result, while a passing check does not produce xpass unless the test is already marked with @pytest.mark.xfail.
  • (docs) Document xfail support for check helper functions in the README.

v2.7.7

Compare Source

Fixed
  • Allow CheckContextManager to catch any exception, not just AssertionError (#​198).
    Non-assertion exceptions (IndexError, KeyError, AttributeError, etc.) are now properly caught and reported as check failures.

v2.7.6

Compare Source

Fixed
  • (typing) Set comparison function types such that None is not allowed

v2.7.5

Compare Source

Changed
  • Passing None to comparison functions like greater(), less(), etc. used to raise an exception, which caused a test failure and stopped the test.
  • That's unexpected with a check function.
  • So now the check fails with a meaningful error message and continues with the rest of the test.
  • (typing) Allow numpy floats with comparison functions to pass mypy.

v2.7.4

Compare Source

Fixed
  • (typing) Allow mixed int/float arguments in strict mypy for comparison helpers by adding float numeric overloads for greater(), greater_equal(), less(), and less_equal() in check_functions.py.

v2.7.3

Compare Source

Added
  • Add __init__.pyi stub file for IDE intellisense (e.g. VSCode) and static type checkers.
  • Add PEP 561 py.typed marker so the package is recognized as typed.
  • (examples) Add test_example_mypy.py to validate import pytest_check as check with mypy.
Fixed
  • Ignore dist-packages in pseudo stack trace - Fixes #​196 - Thanks @​siferati
  • (typing) Resolve remaining mypy errors for import pytest_check as check usage; internal adjustments in check_functions.py.
Changed
  • (ci) Rename "quality" job to "static-analysis"; split into separate jobs for static-analysis, pytest_earliest, and coverage; use Python 3.14 for quality jobs.
  • (tox) Add mypy env coverage for import-as style in examples.

v2.7.2

Compare Source

Fixed
  • #​184: Fix issues with mypy. The example in this issue now passes mypy. Also mypy is now being tested as part of tox.
  • (typing) Allow dynamic helper access on CheckContextManager for static analysis, so patterns like check.equal(...) type-check in fixture-annotated tests.
Changed
  • (typing) Update internal _Comparable* protocol comparison signatures to satisfy strict mypy checks.
  • (tox) Enable and expand mypy env checks to include examples/.
  • (tox) Install httpx in the mypy env so example type checking works without import ignores.
  • (examples) Switch decorator usage in test_example_check_func_decorator.py to import check_func directly for static type checking.
  • (examples) Add test_example_context_manager_type.py to document and validate context-manager fixture typing behavior.
  • (ci) Add a GitHub Actions quality job to run tox -e lint,mypy,pytest_earliest,coverage.

v2.7.1

Compare Source

Added
  • (docs) Document custom message support (msg) in check.raises().
  • (tests) Add tests for custom messages in check.raises().
  • (docs) Document that built-in check methods return bool values.
  • (docs) Update pseudo-traceback examples to reflect the default single pseudo-traceback and show how to increase it with --check-max-tb=5.
  • (docs) Add check.call_on_fail() section with usage guidance.
  • (examples) Add runnable logging example in examples/logging_to_a_file/.
Fixed
  • (tests) Make test_raises_custom_msg compatible with pytest < 7.3 short-summary output.

v2.7.0

Compare Source

Added
  • Support for raises parameter in @pytest.mark.xfail when using check context managers - Fixes #​145 - Thanks @​shairoth12
Fixed
  • Fix #​190: pyright errors
  • Fix #​145: Is the 'raises' parameter in xfail ignored? - not anymore
Changed

v2.6.2

Compare Source

Fixed
Changed
  • (internal) Updated publish pipeline: repository_url -> repository-url

v2.6.0

Compare Source

Added
  • raises returns the exception value, so the expected error message can be verified. - Thanks @​shairoth12

v2.5.4

Compare Source

Changed
  • raises & any_failures exported from top init.py module so that mypy does not complain that they are not explicitly exported. - Thanks @​dpinol
  • Make _Comparable* protocols compatible with builtins - Thanks @​SebastianGrans
  • Turn on testing for Python 3.14 in CI

v2.5.3

Compare Source

Changed
  • Relative paths in tracebacks
  • Add testing of Python 3.14

v2.5.2

Compare Source

Fixed
  • Fixes a weird corner case where an internal error could be generated by (1) having a session scope fixture fail in teardown and (2) having the last test in the session be skipped. Thanks @​asyash26 for reporting and creating reproduction steps. Resolves #​170

v2.5.1

Compare Source

Fixed

v2.5.0

Compare Source

Changed
Fixed
pytest-dev/pytest-cov (pytest-cov)

v7.1.0

Compare Source

  • Fixed total coverage computation to always be consistent, regardless of reporting settings.
    Previously some reports could produce different total counts, and consequently can make --cov-fail-under behave different depending on
    reporting options.
    See #&#8203;641 <https://github.com/pytest-dev/pytest-cov/issues/641>_.

  • Improve handling of ResourceWarning from sqlite3.

    The plugin adds warning filter for sqlite3 ResourceWarning unclosed database (since 6.2.0).
    It checks if there is already existing plugin for this message by comparing filter regular expression.
    When filter is specified on command line the message is escaped and does not match an expected message.
    A check for an escaped regular expression is added to handle this case.

    With this fix one can suppress ResourceWarning from sqlite3 from command line::

    pytest -W "ignore:unclosed database in <sqlite3.Connection object at:ResourceWarning" ...

  • Various improvements to documentation.
    Contributed by Art Pelling in #&#8203;718 <https://github.com/pytest-dev/pytest-cov/pull/718>_ and
    "vivodi" in #&#8203;738 <https://github.com/pytest-dev/pytest-cov/pull/738>.
    Also closed #&#8203;736 <https://github.com/pytest-dev/pytest-cov/issues/736>
    .

  • Fixed some assertions in tests.
    Contributed by in Markéta Machová in #&#8203;722 <https://github.com/pytest-dev/pytest-cov/pull/722>_.

  • Removed unnecessary coverage configuration copying (meant as a backup because reporting commands had configuration side-effects before coverage 5.0).

v7.0.0

Compare Source

  • Dropped support for subprocesses measurement.

    It was a feature added long time ago when coverage lacked a nice way to measure subprocesses created in tests.
    It relied on a .pth file, there was no way to opt-out and it created bad interactions
    with coverage's new patch system <https://coverage.readthedocs.io/en/latest/config.html#run-patch>_ added
    in 7.10 <https://coverage.readthedocs.io/en/7.10.6/changes.html#version-7-10-0-2025-07-24>_.

    To migrate to this release you might need to enable the suprocess patch, example for .coveragerc:

    .. code-block:: ini

    [run]
    patch = subprocess

    This release also requires at least coverage 7.10.6.

  • Switched packaging to have metadata completely in pyproject.toml and use hatchling <https://pypi.org/project/hatchling/>_ for
    building.
    Contributed by Ofek Lev in #&#8203;551 <https://github.com/pytest-dev/pytest-cov/pull/551>_
    with some extras in #&#8203;716 <https://github.com/pytest-dev/pytest-cov/pull/716>_.

  • Removed some not really necessary testing deps like six.

v6.3.0

Compare Source

  • Added support for markdown reports.
    Contributed by Marcos Boger in #&#8203;712 <https://github.com/pytest-dev/pytest-cov/pull/712>_
    and #&#8203;714 <https://github.com/pytest-dev/pytest-cov/pull/714>_.
  • Fixed some formatting issues in docs.
    Anonymous contribution in #&#8203;706 <https://github.com/pytest-dev/pytest-cov/pull/706>_.

v6.2.1

Compare Source

  • Added a version requirement for pytest's pluggy dependency (1.2.0, released 2023-06-21) that has the required new-style hookwrapper API.

  • Removed deprecated license classifier (packaging).

  • Disabled coverage warnings in two more situations where they have no value:

    • "module-not-measured" in workers
    • "already-imported" in subprocesses

v6.2.0

Compare Source

  • The plugin now adds 3 rules in the filter warnings configuration to prevent common coverage warnings being raised as obscure errors::

    default:unclosed database in <sqlite3.Connection object at:ResourceWarning
    once::PytestCovWarning
    once::CoverageWarning

    This fixes most of the bad interactions that are occurring on pytest 8.4 with filterwarnings=error.

    The plugin will check if there already matching rules for the 3 categories
    (ResourceWarning, PytestCovWarning, CoverageWarning) and message (unclosed database in <sqlite3.Connection object at) before adding the filters.

    This means you can have this in your pytest configuration for complete oblivion (not recommended, if that is not clear)::

    filterwarnings = [
    "error",
    "ignore:unclosed database in <sqlite3.Connection object at:ResourceWarning",
    "ignore::PytestCovWarning",
    "ignore::CoverageWarning",
    ]

v6.1.1

Compare Source

  • Fixed breakage that occurs when --cov-context and the no_cover marker are used together.

v6.1.0

Compare Source

  • Change terminal output to use full width lines for the coverage header.
    Contributed by Tsvika Shapira in #&#8203;678 <https://github.com/pytest-dev/pytest-cov/pull/678>_.
  • Removed unnecessary CovFailUnderWarning. Fixes #&#8203;675 <https://github.com/pytest-dev/pytest-cov/issues/675>_.
  • Fixed the term report not using the precision specified via --cov-precision.

v6.0.0

Compare Source

  • Updated various documentation inaccuracies, especially on subprocess handling.
  • Changed fail under checks to use the precision set in the coverage configuration.
    Now it will perform the check just like coverage report would.
  • Added a --cov-precision cli option that can override the value set in your coverage configuration.
  • Dropped support for now EOL Python 3.8.

Configuration

📅 Schedule: (in timezone Etc/UTC)

  • Branch creation
    • "every weekend"
  • 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 renovate Bot added the PR: Dependencies This PR updates project dependencies. label Oct 31, 2026
@renovate
renovate Bot requested a review from lengau as a code owner October 31, 2026 03:28
@renovate
renovate Bot requested a review from a team October 31, 2026 03:28
@renovate

renovate Bot commented Oct 31, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ 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: uv.lock
Using CPython 3.15.2 interpreter at: /opt/containerbase/tools/python/3.15.2/bin/python3
error: No solution found when resolving dependencies for split (markers: python_full_version >= '3.8.1' and python_full_version < '3.9')
  cause: Because the requested Python version (>=3.8) does not satisfy Python>=3.9 and pytest-check>=3.0.0 depends on Python>=3.9, we can conclude that pytest-check>=3.0.0 cannot be used.
         And because craft-platforms:dev depends on pytest-check>=3.0 and your project requires craft-platforms:dev, we can conclude that your project's requirements are unsatisfiable.

hint: While the active Python version is 3.15, the resolution failed for other Python versions supported by your project. Consider limiting your project's supported Python versions using `requires-python`.

hint: The `requires-python` value (>=3.8) includes Python versions that are not supported by your dependencies (e.g., pytest-check>=3.0.0 only supports >=3.9). Consider using a more restrictive `requires-python` value (like >=3.9).

@lengau lengau closed this Oct 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

PR: Dependencies This PR updates project dependencies.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant