Skip to content
This repository was archived by the owner on Jan 14, 2026. It is now read-only.

⬆️ 🛠️(deps): update dependency pytest to v9 #2302

Closed
renovate wants to merge 1 commit into from
Closed

⬆️ 🛠️(deps): update dependency pytest to v9 #2302

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,7 @@ docs = [
"pydata-sphinx-theme~=0.16",
]
test = [

@llamapreview llamapreview Bot Dec 8, 2025

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 | Confidence: High

The update from pytest 8.2 to 9.0 introduces breaking changes that will immediately affect the entire test suite. According to the release notes, PytestRemovedIn9Warning deprecation warnings are now errors by default. This is a direct breaking change that will cause test failures if the codebase uses any deprecated features.

P2 | Confidence: High

The update to pytest 9.0 drops support for Python 3.9. While the PR description includes this fact, the pyproject.toml file does not contain a requires-python classifier or constraint. This creates a latent compatibility risk.

Code Suggestion:

[project]
requires-python = ">=3.10"

P2 | Confidence: Medium

Speculative: The compatibility of the pytest-asyncio plugin (pinned at ~=1.0) with pytest 9.0 is not guaranteed by this PR. While both projects are mature, a major version bump in the core framework can sometimes expose incompatibilities in plugins. The test suite should be run to ensure async tests continue to execute correctly.

P2 | Confidence: Medium

The PR description notes that pytest 9.0 introduces a "strict mode" enabled by a new strict configuration option, which consolidates several existing strictness flags. The project's existing pytest.ini or pyproject.toml configuration might be affected. If the project uses --strict-markers, --strict-config, or xfail_strict, these are now aliased under the strict umbrella. The update could subtly change test behavior if a configuration file uses the old flags and does not account for the new hierarchy. A review of the project's pytest configuration file is recommended.

P2 | Confidence: Low

Speculative: The update bumps minimum requirements on transitive dependencies iniconfig to 1.0.1 and packaging to 22.0.0. While Renovate handles the direct dependency, there is a potential for version conflicts if other project dependencies pin older versions of packaging. This could lead to a conflicted lock file or runtime issues.

"pytest~=8.2",
"pytest~=9.0",
"pytest-asyncio~=1.0",
"pytest-cov~=7.0",
"pytest-loguru~=0.4",
Expand Down
Loading