Repository navigation
build(deps): update development dependencies (major versions) (main) (major) - #287
Closed
renovate[bot] wants to merge 1 commit into
Closed
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/main-major-dev-dependencies
branch
from
October 25, 2026 23:01
3eeaf27 to
96b7f9e
Compare
Contributor
Author
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
~=2.3→~=3.0~=5.0→~=7.1Release Notes
okken/pytest-check (pytest-check)
v3.0.3Compare Source
Fixed
v3.0.2Compare Source
Fixed
unittest.IsolatedAsyncioTestCasetests (issue #210).Developer Experience
tox -p.v3.0.1Compare Source
Fixed
-lor-lv, while preserving full values with-lvv(issue #208). Thanks Neallin-917v3.0.0Compare Source
Highlights
pytest-run-parallel,pytest-swarm, orpytest-freethreaded.Migration Notes
check_logfrom a worker thread, its failure state is now independent of other concurrently running threads.Changed
Fixed
pytest-swarm,pytest-freethreaded, andpytest-run-parallel.v2.10.1Compare Source
Highlights
-xandcheck.raises(), PR #205Changed
Fixed
v2.9.1Compare Source
Fixed
v2.8.0Compare Source
Added
raises(), to accept anxfailreason. 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.xfailsupport for check helper functions in the README.v2.7.7Compare Source
Fixed
Non-assertion exceptions (IndexError, KeyError, AttributeError, etc.) are now properly caught and reported as check failures.
v2.7.6Compare Source
Fixed
v2.7.5Compare Source
Changed
Noneto comparison functions likegreater(),less(), etc. used to raise an exception, which caused a test failure and stopped the test.v2.7.4Compare Source
Fixed
int/floatarguments in strict mypy for comparison helpers by addingfloatnumeric overloads forgreater(),greater_equal(),less(), andless_equal()incheck_functions.py.v2.7.3Compare Source
Added
__init__.pyistub file for IDE intellisense (e.g. VSCode) and static type checkers.py.typedmarker so the package is recognized as typed.test_example_mypy.pyto validateimport pytest_check as checkwith mypy.Fixed
import pytest_check as checkusage; internal adjustments incheck_functions.py.Changed
v2.7.2Compare Source
Fixed
CheckContextManagerfor static analysis, so patterns likecheck.equal(...)type-check in fixture-annotated tests.Changed
_Comparable*protocol comparison signatures to satisfy strict mypy checks.mypyenv checks to includeexamples/.httpxin themypyenv so example type checking works without import ignores.test_example_check_func_decorator.pyto importcheck_funcdirectly for static type checking.test_example_context_manager_type.pyto document and validate context-manager fixture typing behavior.tox -e lint,mypy,pytest_earliest,coverage.v2.7.1Compare Source
Added
msg) incheck.raises().check.raises().boolvalues.--check-max-tb=5.check.call_on_fail()section with usage guidance.examples/logging_to_a_file/.Fixed
test_raises_custom_msgcompatible with pytest < 7.3 short-summary output.v2.7.0Compare Source
Added
raisesparameter in@pytest.mark.xfailwhen using check context managers - Fixes #145 - Thanks @shairoth12Fixed
Changed
v2.6.2Compare Source
Fixed
Changed
v2.6.0Compare Source
Added
raisesreturns the exception value, so the expected error message can be verified. - Thanks @shairoth12v2.5.4Compare Source
Changed
v2.5.3Compare Source
Changed
v2.5.2Compare Source
Fixed
v2.5.1Compare Source
Fixed
v2.5.0Compare Source
Changed
Fixed
pytest-dev/pytest-cov (pytest-cov)
v7.1.0Compare 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
#​641 <https://github.com/pytest-dev/pytest-cov/issues/641>_.Improve handling of ResourceWarning from sqlite3.
The plugin adds warning filter for sqlite3
ResourceWarningunclosed 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
ResourceWarningfrom sqlite3 from command line::pytest -W "ignore:unclosed database in <sqlite3.Connection object at:ResourceWarning" ...
Various improvements to documentation.
Contributed by Art Pelling in
#​718 <https://github.com/pytest-dev/pytest-cov/pull/718>_ and"vivodi" in
#​738 <https://github.com/pytest-dev/pytest-cov/pull/738>.Also closed
#​736 <https://github.com/pytest-dev/pytest-cov/issues/736>.Fixed some assertions in tests.
Contributed by in Markéta Machová in
#​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.0Compare 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
.pthfile, there was no way to opt-out and it created bad interactionswith
coverage's new patch system <https://coverage.readthedocs.io/en/latest/config.html#run-patch>_ addedin
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.tomland usehatchling <https://pypi.org/project/hatchling/>_ forbuilding.
Contributed by Ofek Lev in
#​551 <https://github.com/pytest-dev/pytest-cov/pull/551>_with some extras in
#​716 <https://github.com/pytest-dev/pytest-cov/pull/716>_.Removed some not really necessary testing deps like
six.v6.3.0Compare Source
Contributed by Marcos Boger in
#​712 <https://github.com/pytest-dev/pytest-cov/pull/712>_and
#​714 <https://github.com/pytest-dev/pytest-cov/pull/714>_.Anonymous contribution in
#​706 <https://github.com/pytest-dev/pytest-cov/pull/706>_.v6.2.1Compare 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:
v6.2.0Compare 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.1Compare Source
--cov-contextand theno_covermarker are used together.v6.1.0Compare Source
Contributed by Tsvika Shapira in
#​678 <https://github.com/pytest-dev/pytest-cov/pull/678>_.#​675 <https://github.com/pytest-dev/pytest-cov/issues/675>_.--cov-precision.v6.0.0Compare Source
Now it will perform the check just like
coverage reportwould.--cov-precisioncli option that can override the value set in your coverage configuration.Configuration
📅 Schedule: (in timezone Etc/UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.