NotificationsYou must be signed in to change notification settings
Fork673
Star2.4k

chore(deps): update all non-major dependencies#3213

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Merged

nejch merged 1 commit intomainfromrenovate/all-minor-patch

Jun 10, 2025

Merged

chore(deps): update all non-major dependencies#3213

nejch merged 1 commit intomainfromrenovate/all-minor-patch

Jun 10, 2025

Conversation

Copy link

Contributor

renovatebot commentedJun 9, 2025•
edited
Loading

This PR contains the following updates:

Package	Change	Type	Update
commitizen (changelog)	`==4.8.2` ->`==4.8.3`		patch
commitizen-tools/commitizen	`v4.8.2` ->`v4.8.3`	repository	patch
maxbrunet/pre-commit-renovate	`40.31.0` ->`40.49.0`	repository	minor
pre-commit/mirrors-mypy	`v1.15.0` ->`v1.16.0`	repository	minor
pytest (changelog)	`==8.3.5` ->`==8.4.0`		minor
pytest-docker	`==3.2.1` ->`==3.2.2`		patch
python	`3.12-alpine` ->`3.13-alpine`	final	minor
python	`3.12-alpine` ->`3.13-alpine`	stage	minor
types-requests (changelog)	`==2.32.0.20250515` ->`==2.32.0.20250602`		patch
types-setuptools (changelog)	`==80.8.0.20250521` ->`==80.9.0.20250529`		minor

Note: Thepre-commit manager in Renovate is not supported by thepre-commit maintainers or community. Please do not report any problems there, insteadcreate a Discussion in the Renovate repository if you have any questions.

Release Notes

commitizen-tools/commitizen (commitizen)

`v4.8.3`

Compare Source

Fix

cli: update description for deprecate warning
commit: emit deprecated warning of cz commit -s
Check: make parameters backward compatible
BaseConfig: mypy error
deprecated: mark deprecate in v5
defaults: add non-capitalized default constants back and deprecated warning

Refactor

jira: refactor message
conventional_commits: use TypedDict for answers
conventional_commits: make schema_pattern more readable
do not guess if changelog format is provided
check: compile once and rename variable
questions: type questions with TypedDict
bump: simplify nested if
git: retype get_commits parameter to make it more friendly to call sites
git: simplify tag logic
bump: eliminate similar patterns in code
bump: use any to replace 'or' chain
remove unnecessary bool() and remove Any type from TypedDict get
bump: improve readability and still bypass mypy check
commands: remove unused args, type version command args
commit: type commit args
check: type CheckArgs arguments
check: remove unused argument
changelog: type untyped arguments
bump: TypedDict for bump argument
make methods protected, better type
conventional_commits: remove unnecessary checks
fix mypy output and better type
BaseCommitizen: remove unused process_commit
removeTypeError handling sincePython >=3.9 is required
add comment clarifyingno_raise parsing tolist[int]
cli.py: add type hints
mypy: removeunused-ignore
changelog: better typing, yield
cli: early return and improve test coverage
git: extract _create_commit_cmd_string
misc cleanup
bump: clean up
bump: add type for out, replace function with re escape
BaseConfig: use setter
changelog: minor cleanup
git: refactor get_tag_names
EOLType: add eol enum back and reorganize methods
git: code cleanup and better test coverage
commit: simplify call
version_scheme: cleanup
improve readability and fix typos

Perf

bump: avoid unnecessary list construction and rename variable to avoid confusion
tags: use set

maxbrunet/pre-commit-renovate (maxbrunet/pre-commit-renovate)

pre-commit/mirrors-mypy (pre-commit/mirrors-mypy)

`v1.16.0`

Compare Source

pytest-dev/pytest (pytest)

`v8.4.0`

Compare Source

pytest 8.4.0 (2025-06-02)

Removals and backward incompatible breaking changes

#11372: Async tests will now fail, instead of warning+skipping, if you don't have any suitable plugin installed.
#12346: Tests will now fail, instead of raising a warning, if they return any value other than None.
#12874: We dropped support for Python 3.8 following its end of life (2024-10-07).
#12960: Test functions containing a yield now cause an explicit error. They have not been run since pytest 4.0, and were previously marked as an expected failure and deprecation warning.
Seethe docs <yield tests deprecated>{.interpreted-text role="ref"} for more information.

Deprecations (removal in next major release)

#10839: Requesting an asynchronous fixture without a [pytest_fixture_setup]{.title-ref} hook that resolves it will now give a DeprecationWarning. This most commonly happens if a sync test requests an async fixture. This should have no effect on a majority of users with async tests or fixtures using async pytest plugins, but may affect non-standard hook setups orautouse=True. For guidance on how to work around this warning seesync-test-async-fixture{.interpreted-text role="ref"}.

New features

#11538: Addedpytest.RaisesGroup{.interpreted-text role="class"} as an equivalent topytest.raises{.interpreted-text role="func"} for expectingExceptionGroup{.interpreted-text role="exc"}. Also addspytest.RaisesExc{.interpreted-text role="class"} which is now the logic behindpytest.raises{.interpreted-text role="func"} and used as parameter topytest.RaisesGroup{.interpreted-text role="class"}.RaisesGroup includes the ability to specify multiple different expected exceptions, the structure of nested exception groups, and flags for emulatingexcept* <except_star>{.interpreted-text role="ref"}. Seeassert-matching-exception-groups{.interpreted-text role="ref"} and docstrings for more information.
#12081: Addedcapteesys{.interpreted-text role="fixture"} to capture AND pass output to next handler set by--capture=.
#12504:pytest.mark.xfail{.interpreted-text role="func"} now acceptspytest.RaisesGroup{.interpreted-text role="class"} for theraises parameter when you expect an exception group. You can also pass apytest.RaisesExc{.interpreted-text role="class"} if you e.g. want to make use of thecheck parameter.
#12713: New [--force-short-summary]{.title-ref} option to force condensed summary output regardless of verbosity level.
This lets users still see condensed summary output of failures for quick reference in log files from job outputs, being especially useful if non-condensed output is very verbose.
#12749: pytest traditionally collects classes/functions in the test module namespace even if they are imported from another file.
For example:

contents of src/domain.py

class Testament: ...

contents of tests/test_testament.py

from domain import Testamentdef test_testament(): ...```In this scenario with the default options, pytest will collect the class [Testament]{.title-ref} from [tests/test_testament.py]{.title-ref} because it starts with [Test]{.title-ref}, even though in this case it is a production class being imported in the test module namespace.This behavior can now be prevented by setting the new `collect_imported_tests`{.interpreted-text role="confval"} configuration option to `false`, which will make pytest collect classes/functions from test files **only** if they are defined in that file.\-- by `FreerGit`{.interpreted-text role="user"}

#12765: Thresholds to trigger snippet truncation can now be set withtruncation_limit_lines{.interpreted-text role="confval"} andtruncation_limit_chars{.interpreted-text role="confval"}.
Seetruncation-params{.interpreted-text role="ref"} for more information.
#13125:console_output_style{.interpreted-text role="confval"} now supportstimes to show execution time of each test.
#13192:pytest.raises{.interpreted-text role="func"} will now raise a warning when passing an empty string tomatch, as this will match against any value. Usematch="^$" if you want to check that an exception has no message.
#13192:pytest.raises{.interpreted-text role="func"} will now print a helpful string diff if matching fails and the match parameter has^ and$ and is otherwise escaped.
#13192: You can now passwith pytest.raises(check=fn): <pytest.raises>{.interpreted-text role="func"}, wherefn is a function which takes a raised exception and returns a boolean. Theraises fails if no exception was raised (as usual), passes if an exception is raised andfn returnsTrue (as well asmatch and the type matching, if specified, which are checked before), and propagates the exception iffn returnsFalse (which likely also fails the test).
#13228:hidden-param{.interpreted-text role="ref"} can now be used inid ofpytest.param{.interpreted-text role="func"} or in
ids ofMetafunc.parametrize <pytest.Metafunc.parametrize>{.interpreted-text role="py:func"}.
It hides the parameter set from the test name.
#13253: New flag:--disable-plugin-autoload <disable_plugin_autoload>{.interpreted-text role="ref"} which works as an alternative toPYTEST_DISABLE_PLUGIN_AUTOLOAD{.interpreted-text role="envvar"} when setting environment variables is inconvenient; and allows setting it in config files withaddopts{.interpreted-text role="confval"}.

Improvements in existing functionality

#10224: pytest'sshort andlong traceback styles (how-to-modifying-python-tb-printing{.interpreted-text role="ref"})
now have partial657{.interpreted-text role="pep"} support and will show specific code segments in the
traceback.

================================= FAILURES =================================_______________________ test_gets_correct_tracebacks _______________________test_tracebacks.py:12: in test_gets_correct_tracebacks    assert manhattan_distance(p1, p2) == 1           ^^^^^^^^^^^^^^^^^^^^^^^^^^test_tracebacks.py:6: in manhattan_distance    return abs(point_1.x - point_2.x) + abs(point_1.y - point_2.y)                           ^^^^^^^^^E   AttributeError: 'NoneType' object has no attribute 'x'

-- byammaraskar{.interpreted-text role="user"}

#11118: Nowpythonpath{.interpreted-text role="confval"} configures [$PYTHONPATH]{.title-ref} earlier than before during the initialization process, which now also affects plugins loaded via the [-p]{.title-ref} command-line option.
-- bymillerdev{.interpreted-text role="user"}
#11381: Thetype parameter of theparser.addini method now accepts ["int"]{.title-ref} and"float" parameters, facilitating the parsing of configuration values in the configuration file.
Example:
```
defpytest_addoption(parser):parser.addini("int_value",type="int",default=2,help="my int value")parser.addini("float_value",type="float",default=4.2,help="my float value")
```
The [pytest.ini]{.title-ref} file:
```
[pytest]int_value = 3float_value = 5.4
```
#11525: Fixtures are now clearly represented in the output as a "fixture object", not as a normal function as before, making it easy for beginners to catch mistakes such as referencing a fixture declared in the same module but not requested in the test function.
-- bythe-compiler{.interpreted-text role="user"} andglyphack{.interpreted-text role="user"}
#12426: A warning is now issued whenpytest.mark.usefixtures ref{.interpreted-text role="ref"} is used without specifying any fixtures. Previously, empty usefixtures markers were silently ignored.
#12707: Exception chains can be navigated when dropped into Pdb in Python 3.13+.
#12736: Added a new attribute [name]{.title-ref} with the fixed value ["pytest tests"]{.title-ref} to the root tag [testsuites]{.title-ref} of the junit-xml generated by pytest.
This attribute is part of many junit-xml specifications and is even part of the [junit-10.xsd]{.title-ref} specification that pytest's implementation is based on.
#12943: If a test fails with an exceptiongroup with a single exception, the contained exception will now be displayed in the short test summary info.
#12958: A number ofunraisable <unraisable>{.interpreted-text role="ref"} enhancements:
- Set the unraisable hook as early as possible and unset it as late as possible, to collect the most possible number of unraisable exceptions.
- Call the garbage collector just before unsetting the unraisable hook, to collect any straggling exceptions.
- Collect multiple unraisable exceptions per test phase.
- Report thetracemalloc{.interpreted-text role="mod"} allocation traceback (if available).
- Avoid using a generator based hook to allow handlingStopIteration{.interpreted-text role="class"} in test failures.
- Report the unraisable exception as the cause of thepytest.PytestUnraisableExceptionWarning{.interpreted-text role="class"} exception if raised.
- Compute therepr of the unraisable object in the unraisable hook so you get the latest information if available, and should help with resurrection of the object.
#13010:pytest.approx{.interpreted-text role="func"} now can compare collections that contain numbers and non-numbers mixed.
#13016: A number ofthreadexception <unraisable>{.interpreted-text role="ref"} enhancements:
- Set the excepthook as early as possible and unset it as late as possible, to collect the most possible number of unhandled exceptions from threads.
- Collect multiple thread exceptions per test phase.
- Report thetracemalloc{.interpreted-text role="mod"} allocation traceback (if available).
- Avoid using a generator based hook to allow handlingStopIteration{.interpreted-text role="class"} in test failures.
- Report the thread exception as the cause of thepytest.PytestUnhandledThreadExceptionWarning{.interpreted-text role="class"} exception if raised.
- Extract thename of the thread object in the excepthook which should help with resurrection of the thread.
#13031: An empty parameter set as inpytest.mark.parametrize([], ids=idfunc) will no longer trigger a call toidfunc with internal objects.
#13115: Allows supplyingExceptionGroup[Exception] andBaseExceptionGroup[BaseException] topytest.raises to keep full typing onExceptionInfo <pytest.ExceptionInfo>{.interpreted-text role="class"}:
```
withpytest.raises(ExceptionGroup[Exception])asexc_info:some_function()
```
Parametrizing with other exception types remains an error - we do not check the types of child exceptions and thus do not permit code that might look like we do.
#13122: The--stepwise mode received a number of improvements:
- It no longer forgets the last failed test in case pytest is executed later without the flag.
  This enables the following workflow:
  1. Execute pytest with--stepwise, pytest then stops at the first failing test;
  2. Iteratively update the code and run the test in isolation, without the--stepwise flag (for example in an IDE), until it is fixed.
  3. Execute pytest with--stepwise again and pytest will continue from the previously failed test, and if it passes, continue on to the next tests.
  Previously, at step 3, pytest would start from the beginning, forgetting the previously failed test.
  This change however might cause issues if the--stepwise mode is used far apart in time, as the state might get stale, so the internal state will be reset automatically in case the test suite changes (for now only the number of tests are considered for this, we might change/improve this on the future).
- New--stepwise-reset/--sw-reset flag, allowing the user to explicitly reset the stepwise state and restart the workflow from the beginning.
#13308: Added official support for Python 3.14.
#13380: FixExceptionGroup{.interpreted-text role="class"} traceback filtering to exclude pytest internals.
#13415: The author metadata of the BibTex example is now correctly formatted with last names following first names.
An example of BibLaTex has been added.
BibTex and BibLaTex examples now clearly indicate that what is cited is software.
-- bywillynilly{.interpreted-text role="user"}
#13420: Improved test collection performance by optimizing path resolution used inFSCollector.
#13457: The error message about duplicate parametrization no longer displays an internal stack trace.
#4112: Usingpytest.mark.usefixtures <pytest.mark.usefixtures ref>{.interpreted-text role="ref"} onpytest.param{.interpreted-text role="func"} now produces an error instead of silently doing nothing.
#5473: Replace [:]{.title-ref} with [;]{.title-ref} in the assertion rewrite warning message so it can be filtered using standard Python warning filters before callingpytest.main{.interpreted-text role="func"}.

[#&#8203;6985](https://redirect.github.com/pytest-dev/pytest/issues/6985): Improved `pytest.approx`{.interpreted-text role="func"} to enhance the readability of value ranges and tolerances between 0.001 and 1000.:   -   The [repr]{.title-ref} method now provides clearer output for values within those ranges, making it easier to interpret the results.    -   Previously, the output for those ranges of values and tolerances was displayed in scientific notation (e.g., [42 ± 1.0e+00]{.title-ref}). The updated method now presents the tolerance as a decimal for better readability (e.g., [42 ± 1]{.title-ref}).        Example:        **Previous Output:**        ``` console        >>> pytest.approx(42, abs=1)        42 ± 1.0e+00        ```        **Current Output:**        ``` console        >>> pytest.approx(42, abs=1)        42 ± 1        ```    \-- by `fazeelghafoor`{.interpreted-text role="user"}

#7683: The formerly optionalpygments dependency is now required, causing output always to be source-highlighted (unless disabled via the--code-highlight=no CLI option).

Bug fixes

#10404: Apply filterwarnings from config/cli as soon as possible, and revert them as late as possible
so that warnings as errors are collected throughout the pytest run and before the
unraisable and threadexcept hooks are removed.
This allows very late warnings and unraisable/threadexcept exceptions to fail the test suite.
This also changes the warning that the lsof plugin issues from PytestWarning to the new warning PytestFDWarning so it can be more easily filtered.
#11067: The test report is now consistent regardless if the test xfailed viapytest.mark.xfail <pytest.mark.xfail ref>{.interpreted-text role="ref"} orpytest.fail{.interpreted-text role="func"}.
Previously,xfailed tests via the marker would have the string"reason: " prefixed to the message, while thosexfailed via the function did not. The prefix has been removed.
#12008: In11220{.interpreted-text role="pr"}, an unintended change in reordering was introduced by changing the way indices were assigned to direct params. More specifically, before that change, the indices of direct params to metafunc's callspecs were assigned after all parametrizations took place. Now, that change is reverted.
#12863: Fix applying markers, includingpytest.mark.parametrize <pytest.mark.parametrize ref>{.interpreted-text role="ref"} when placed above [@staticmethod]{.title-ref} or [@classmethod]{.title-ref}.
#12929: Handle StopIteration from test cases, setup and teardown correctly.
#12938: Fixed--durations-min argument not respected if-vv is used.
#12946: Fixed missing help forpdb{.interpreted-text role="mod"} commands wrapped by pytest -- byadamchainz{.interpreted-text role="user"}.
#12981: Prevent exceptions inpytest.Config.add_cleanup{.interpreted-text role="func"} callbacks preventing further cleanups.
#13047: Restorepytest.approx{.interpreted-text role="func"} handling of equality checks between [bool]{.title-ref} and [numpy.bool_]{.title-ref} types.
Comparing [bool]{.title-ref} and [numpy.bool_]{.title-ref} usingpytest.approx{.interpreted-text role="func"} accidentally changed in version [8.3.4]{.title-ref} and [8.3.5]{.title-ref} to no longer match:
```
>>>import numpyas np>>>from pytestimport approx>>> [np.True_, np.True_]== pytest.approx([True,True])False
```
This has now been fixed:
```
>>> [np.True_, np.True_]== pytest.approx([True,True])True
```
#13119: Improved handling of invalid regex patterns for filter warnings by providing a clear error message.
#13175: The diff is now also highlighted correctly when comparing two strings.
#13248: Fixed an issue where passing ascope inMetafunc.parametrize <pytest.Metafunc.parametrize>{.interpreted-text role="py:func"} withindirect=True
could result in other fixtures being unable to depend on the parametrized fixture.
#13291: Fixedrepr ofattrs objects in assertion failure messages when usingattrs>=25.2.
#13312: Fixed a possibleKeyError crash on PyPy during collection of tests involving higher-scoped parameters.
#13345: Fix type hints forpytest.TestReport.when{.interpreted-text role="attr"} andpytest.TestReport.location{.interpreted-text role="attr"}.
#13377: Fixed handling of test methods with positional-only parameter syntax.
Now, methods are supported that formally defineself as positional-only
and/or fixture parameters as keyword-only, e.g.:
```
classTestClass:deftest_method(self,/,*,fixture): ...
```
Before, this caused an internal error in pytest.
#13384: Fixed an issue where pytest could report negative durations.
#13420: Addedlru_cache tonodes._check_initialpaths_for_relpath.
#9037: Honordisable_test_id_escaping_and_forfeit_all_rights_to_community_support{.interpreted-text role="confval"} when escaping ids in parametrized tests.

Improved documentation

#12535: [This
example]{.title-ref}<https://docs.pytest.org/en/latest/example/simple.html#making-test-result-information-available-in-fixtures>
showedprint statements that do not exactly reflect what the
different branches actually do. The fix makes the example more precise.
#13218: Pointed out in thepytest.approx{.interpreted-text role="func"} documentation that it considers booleans unequal to numeric zero or one.
#13221: Improved grouping of CLI options in the--help output.
#6649: Added~pytest.TerminalReporter{.interpreted-text role="class"} to theapi-reference{.interpreted-text role="ref"} documentation page.
#8612: Add a recipe for handling abstract test classes in the documentation.
A new example has been added to the documentation to demonstrate how to use a mixin class to handle abstract
test classes without manually setting the__test__ attribute for subclasses.
This ensures that subclasses of abstract test classes are automatically collected by pytest.

Packaging updates and notes for downstreams

#13317: Specified minimum allowed versions ofcolorama,iniconfig,
andpackaging; and bumped the minimum allowed version
ofexceptiongroup forpython_version<'3.11' from a release
candidate to a full release.

Contributor-facing changes

#12017: Mixed internal improvements:
- Migrate formatting to f-strings in some tests.
- Use type-safe constructs in JUnitXML tests.
- MovedMockTiming into_pytest.timing.
-- byRonnyPfannschmidt{.interpreted-text role="user"}
#12647: Fixed running the test suite with thehypothesis pytest plugin.

Miscellaneous internal changes

#6649: Added~pytest.TerminalReporter{.interpreted-text role="class"} to the public pytest API, as it is part of the signature of thepytest_terminal_summary{.interpreted-text role="hook"} hook.

avast/pytest-docker (pytest-docker)