-
Notifications
You must be signed in to change notification settings - Fork 30
Scheduled weekly dependency update for week 20 #694
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
98badf8
Update sphinx-autodoc-typehints from 3.9.9 to 3.10.2
pyup-bot 139d6da
Update setuptools from 80.9.0 to 82.0.1
pyup-bot ce595e9
Update pytest from 8.3.5 to 9.0.3
pyup-bot a170cc8
Update respx from 0.22.0 to 0.23.1
pyup-bot b06aa96
Update pytest-env from 1.1.5 to 1.6.0
pyup-bot af4f5a2
Update pytest-mock from 3.14.0 to 3.15.1
pyup-bot 523facc
Update fiftyone from 1.5.2 to 1.15.0
pyup-bot 66af9ff
Update datasets from 3.6.0 to 4.8.5
pyup-bot e9309d2
Update ultralytics from 8.3.237 to 8.4.51
pyup-bot File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,9 +1,9 @@ | ||
| setuptools==80.9.0 | ||
| pytest==8.3.5 | ||
| respx==0.22.0 | ||
| setuptools==82.0.1 | ||
| pytest==9.0.3 | ||
| respx==0.23.1 | ||
| pytest-git==1.8.0 | ||
| pytest-env==1.1.5 | ||
| pytest-mock==3.14.0 | ||
| fiftyone==1.5.2 | ||
| datasets==3.6.0 | ||
| ultralytics==8.3.237 | ||
| pytest-env==1.6.0 | ||
| pytest-mock==3.15.1 | ||
| fiftyone==1.15.0 | ||
| datasets==4.8.5 | ||
| ultralytics==8.4.51 | ||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
pytest 9.0.0 breaking changes and migration guide💡 Result:
Pytest 9.0.0 was released on November 5, 2025 [1][2][3]. As a major version release, it introduced several significant changes, including the removal of deprecated features and the introduction of new capabilities [4][2]. Key Changes and Migration Considerations: 1. Python Version Support: Pytest 9.0.0 requires Python 3.10 or newer [5]. If your environment uses an older version of Python (such as 3.9 or earlier), you must upgrade your Python interpreter before migrating to pytest 9.0.0 [6]. 2. Native TOML Configuration: Pytest 9.0.0 introduced support for native TOML configuration files [4][7]. - You can now use a [tool.pytest] table in your pyproject.toml file, or use a dedicated pytest.toml or.pytest.toml file [7]. - While the previous [tool.pytest.ini_options] table remains supported for backward compatibility, you cannot use both the native [tool.pytest] table and the legacy [tool.pytest.ini_options] table simultaneously [7]. 3. Experimental Subtests Support: Support for subtests has been integrated into the pytest core [4]. This functionality, previously available via the pytest-subtests plugin, now includes support for unittest.TestCase.subTest [4]. Note that this feature is considered experimental and may evolve in future releases [4]. 4. Deprecations and Removals: As is standard for major releases, pytest 9.0.0 removed various features that were deprecated in previous 8.x versions [4][2]. Users are advised to review the deprecation warnings in their test suites (which should have been visible when running pytest 8.x) to identify and address any code that relies on removed functionality [4][2]. Migration Steps: - Audit your environment: Ensure you are running Python 3.10+. - Check for deprecation warnings: Before upgrading, run your existing test suite with the latest 8.x version of pytest and resolve all deprecation warnings. - Update configuration: If you wish to adopt native TOML configuration, migrate your settings from [tool.pytest.ini_options] to the [tool.pytest] table in your pyproject.toml or a separate.toml file [7]. - Test with the new version: Upgrade to 9.0.0 (or the latest 9.0.x patch release) and verify that your test suite passes. For a comprehensive list of all changes, including specific bug fixes and minor improvements, consult the official pytest changelog [4][1].
Citations:
🏁 Script executed:
Repository: DagsHub/client
Length of output: 80
Pytest 9.0.3 requires Python 3.10+ and removes deprecated features—verify compatibility before merging.
Pytest was upgraded from 8.3.5 to 9.0.3, a major version jump with significant breaking changes:
[tool.pytest]inpyproject.tomlnow required instead of[tool.pytest.ini_options])Before merging, ensure: