← Back to issue list

build(deps): update development dependencies (major versions) (main) (major)

View original Github issue

Metadata

Project
craft-platforms
Number
#289
Type
pull request
State
closed
Author
renovate
Labels
PR: Dependencies
Created
Updated
Closed

Current evaluation

Renovate PR to update pytest-check and pytest-cov was closed due to a uv.lock artifact update failure caused by a Python version conflict.

Resolution: closed stale

Reason: The PR was closed because Renovate failed to update the uv.lock artifact. The dependency resolver reported a conflict: pytest-check 3.0 requires Python >=3.9, which clashes with a transitive dependency requiring Python <3.9.

Evaluated by: mr-cal-bot

No scores available.

Issue body

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [pytest-check](https://redirect.github.com/okken/pytest-check) | `~=2.3` → `~=3.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest-check/3.0.3?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest-check/2.4.2/3.0.3?slim=true) | | [pytest-cov](https://redirect.github.com/pytest-dev/pytest-cov) ([changelog](https://pytest-cov.readthedocs.io/en/latest/changelog.html)) | `~=5.0` → `~=7.1` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest-cov/7.1.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest-cov/5.0.0/7.1.0?slim=true) | --- ### Release Notes <details> <summary>okken/pytest-check (pytest-check)</summary> ### [`v3.0.3`](https://redirect.github.com/okken/pytest-check/blob/HEAD/changelog.md#303---14-Oct-2026) [Compare Source](https://redirect.github.com/okken/pytest-check/compare/3.0.2...3.0.3) ##### Fixed - Second attempt to fix issue [#&#8203;210](https://redirect.github.com/okken/pytest-check/issues/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`](https://redirect.github.com/okken/pytest-check/blob/HEAD/changelog.md#302---13-Oct-2026) [Compare Source](https://redirect.github.com/okken/pytest-check/compare/3.0.1...3.0.2) ##### Fixed - Report failed checks correctly in `unittest.IsolatedAsyncioTestCase` tests (issue [#&#8203;210](https://redirect.github.com/okken/pytest-check/issues/210)). ##### Developer Experience - Split mypy checks into separate tox environments so they can run in parallel with `tox -p`. ### [`v3.0.1`](https://redirect.github.com/okken/pytest-check/blob/HEAD/changelog.md#301---12-Oct-2026) [Compare Source](https://redirect.github.com/okken/pytest-check/compare/3.0.0...3.0.1) ##### Fixed - Truncate long local values in check pseudo tracebacks with `-l` or `-lv`, while preserving full values with `-lvv` (issue [#&#8203;208](https://redirect.github.com/okken/pytest-check/issues/208)). Thanks [Neallin-917](https://redirect.github.com/Neallin-917) ### [`v3.0.0`](https://redirect.github.com/okken/pytest-check/blob/HEAD/changelog.md#300---10-Oct-2026) [Compare Source](https://redirect.github.com/okken/pytest-check/compare/2.10.1...3.0.0) ##### 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](https://redirect.github.com/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`](https://redirect.github.com/okken/pytest-check/blob/HEAD/changelog.md#2101---10-Oct-2026) [Compare Source](https://redirect.github.com/okken/pytest-check/compare/2.9.1...2.10.1) ##### Highlights - Fix call_on_fail() functionality, issue [#&#8203;203](https://redirect.github.com/okken/pytest-check/issues/203) - Fix an issue with `-x` and `check.raises()`, PR [#&#8203;205](https://redirect.github.com/okken/pytest-check/issues/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](https://redirect.github.com/dpinol) ##### Fixed - [#&#8203;203](https://redirect.github.com/okken/pytest-check/issues/203) call_on_fail() no longer registers globally since 2.9.1 - Issue with raises - no issue filed, but this is related to PR [#&#8203;205](https://redirect.github.com/okken/pytest-check/issues/205) - thanks [oyeong011](https://redirect.github.com/oyeong011) ### [`v2.9.1`](https://redirect.github.com/okken/pytest-check/blob/HEAD/changelog.md#291---31-July-2026) [Compare Source](https://redirect.github.com/okken/pytest-check/compare/2.8.0...2.9.1) ##### Fixed - Fix [#&#8203;173: An issue with pytest-reportlog](https://redirect.github.com/okken/pytest-check/issues/173) thanks to a suggestion from MV Seotlo - also the resulting code is a bit cleaner of a solution for the pseudo-traceback code. ### [`v2.8.0`](https://redirect.github.com/okken/pytest-check/blob/HEAD/changelog.md#280---2026-Mar-22) [Compare Source](https://redirect.github.com/okken/pytest-check/compare/2.7.7...2.8.0) ##### Added - Support Request [#&#8203;122: Feature proposal: Capability to mark checks as xfail](https://redirect.github.com/okken/pytest-check/issues/122) - 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`](https://redirect.github.com/okken/pytest-check/blob/HEAD/changelog.md#277---2026-Mar-20) [Compare Source](https://redirect.github.com/okken/pytest-check/compare/2.7.6...2.7.7) ##### Fixed - Allow CheckContextManager to catch any exception, not just AssertionError ([#&#8203;198](https://redirect.github.com/okken/pytest-check/issues/198)). Non-assertion exceptions (IndexError, KeyError, AttributeError, etc.) are now properly caught and reported as check failures. ### [`v2.7.6`](https://redirect.github.com/okken/pytest-check/blob/HEAD/changelog.md#276---2026-Mar-04) [Compare Source](https://redirect.github.com/okken/pytest-check/compare/2.7.5...2.7.6) ##### Fixed - (typing) Set comparison function types such that None is not allowed ### [`v2.7.5`](https://redirect.github.com/okken/pytest-check/blob/HEAD/changelog.md#275---2026-Mar-04) [Compare Source](https://redirect.github.com/okken/pytest-check/compare/2.7.4...2.7.5) ##### 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`](https://redirect.github.com/okken/pytest-check/blob/HEAD/changelog.md#274---2026-Mar-03) [Compare Source](https://redirect.github.com/okken/pytest-check/compare/2.7.3...2.7.4) ##### 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`](https://redirect.github.com/okken/pytest-check/blob/HEAD/changelog.md#273---2026-Mar-02) [Compare Source](https://redirect.github.com/okken/pytest-check/compare/2.7.2...2.7.3) ##### 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 [#&#8203;196](https://redirect.github.com/okken/pytest-check/issues/196) - Thanks [@&#8203;siferati](https://redirect.github.com/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`](https://redirect.github.com/okken/pytest-check/blob/HEAD/changelog.md#272---2026-Feb-27) [Compare Source](https://redirect.github.com/okken/pytest-check/compare/2.7.1...2.7.2) ##### Fixed - [#&#8203;184](https://redirect.github.com/okken/pytest-check/issues/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`](https://redirect.github.com/okken/pytest-check/blob/HEAD/changelog.md#271---2026-Feb-27) [Compare Source](https://redirect.github.com/okken/pytest-check/compare/2.7.0...2.7.1) ##### 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`](https://redirect.github.com/okken/pytest-check/blob/HEAD/changelog.md#270---2026-Feb-24) [Compare Source](https://redirect.github.com/okken/pytest-check/compare/2.6.2...2.7.0) ##### Added - Support for `raises` parameter in `@pytest.mark.xfail` when using check context managers - Fixes [#&#8203;145](https://redirect.github.com/okken/pytest-check/issues/145) - Thanks [@&#8203;shairoth12](https://redirect.github.com/shairoth12) ##### Fixed - Fix [#&#8203;190](https://redirect.github.com/okken/pytest-check/issues/190): pyright errors - Fix [#&#8203;145](https://redirect.github.com/okken/pytest-check/issues/145): Is the 'raises' parameter in xfail ignored? - not anymore ##### Changed - Internal: Add fixture run_example_test in tests - Thanks [@&#8203;even-even](https://redirect.github.com/even-even) - Update **all** to include 'check' in pytest_check module - Fixes [#&#8203;190](https://redirect.github.com/okken/pytest-check/issues/190) - Thanks [@&#8203;taylermulligan](https://redirect.github.com/taylermulligan) ### [`v2.6.2`](https://redirect.github.com/okken/pytest-check/blob/HEAD/changelog.md#262---2025-Nov-28) [Compare Source](https://redirect.github.com/okken/pytest-check/compare/2.6.0...2.6.2) ##### Fixed - Greater/less_equal support numpy scalars [#&#8203;189](https://redirect.github.com/okken/pytest-check/issues/189) - Thanks [@&#8203;dpinol](https://redirect.github.com/dpinol) ##### Changed - (internal) Updated publish pipeline: repository_url -> repository-url ### [`v2.6.0`](https://redirect.github.com/okken/pytest-check/blob/HEAD/changelog.md#260---2025-Oct-6) [Compare Source](https://redirect.github.com/okken/pytest-check/compare/2.5.4...2.6.0) ##### Added - `raises` returns the exception value, so the expected error message can be verified. - Thanks [@&#8203;shairoth12](https://redirect.github.com/shairoth12) ### [`v2.5.4`](https://redirect.github.com/okken/pytest-check/blob/HEAD/changelog.md#254---2025-Sept-14) [Compare Source](https://redirect.github.com/okken/pytest-check/compare/2.5.3...2.5.4) ##### Changed - raises & any_failures exported from top **init**.py module so that mypy does not complain that they are not explicitly exported. - Thanks [@&#8203;dpinol](https://redirect.github.com/dpinol) - Make \_Comparable\* protocols compatible with builtins - Thanks [@&#8203;SebastianGrans](https://redirect.github.com/SebastianGrans) - Turn on testing for Python 3.14 in CI ### [`v2.5.3`](https://redirect.github.com/okken/pytest-check/blob/HEAD/changelog.md#253---2025-Apr-3) [Compare Source](https://redirect.github.com/okken/pytest-check/compare/2.5.2...2.5.3) ##### Changed - Relative paths in tracebacks - PR [#&#8203;179](https://redirect.github.com/okken/pytest-check/issues/179), thanks [@&#8203;dpinol](https://redirect.github.com/dpinol) - Add testing of Python 3.14 ### [`v2.5.2`](https://redirect.github.com/okken/pytest-check/blob/HEAD/changelog.md#252---2025-Mar-29) [Compare Source](https://redirect.github.com/okken/pytest-check/compare/2.5.1...2.5.2) ##### 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 [@&#8203;asyash26](https://redirect.github.com/asyash26) for reporting and creating reproduction steps. Resolves [#&#8203;170](https://redirect.github.com/okken/pytest-check/issues/170) ### [`v2.5.1`](https://redirect.github.com/okken/pytest-check/blob/HEAD/changelog.md#251---2025-Mar-18) [Compare Source](https://redirect.github.com/okken/pytest-check/compare/2.5.0...2.5.1) ##### Fixed - Set a minimum pluggy version during type checking. Resolves [#&#8203;176](https://redirect.github.com/okken/pytest-check/issues/176), thanks [@&#8203;d-ryzhykau](https://redirect.github.com/d-ryzhykau) ### [`v2.5.0`](https://redirect.github.com/okken/pytest-check/blob/HEAD/changelog.md#250---2025-Feb-12) [Compare Source](https://redirect.github.com/okken/pytest-check/compare/2.4.2...2.5.0) ##### Changed - Add type hints, remove support for Python 3.8, resolves [#&#8203;163](https://redirect.github.com/okken/pytest-check/issues/163), thanks [@&#8203;mfulgo](https://redirect.github.com/mfulgo) ##### Fixed - Fixes [#&#8203;171](https://redirect.github.com/okken/pytest-check/issues/171), check doesn't respect runxfail option, thanks [@&#8203;taylermulligan](https://redirect.github.com/taylermulligan) </details> <details> <summary>pytest-dev/pytest-cov (pytest-cov)</summary> ### [`v7.1.0`](https://redirect.github.com/pytest-dev/pytest-cov/blob/HEAD/CHANGELOG.rst#710-2026-03-21) [Compare Source](https://redirect.github.com/pytest-dev/pytest-cov/compare/v7.0.0...v7.1.0) - 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`](https://redirect.github.com/pytest-dev/pytest-cov/blob/HEAD/CHANGELOG.rst#700-2025-09-09) [Compare Source](https://redirect.github.com/pytest-dev/pytest-cov/compare/v6.3.0...v7.0.0) - 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`](https://redirect.github.com/pytest-dev/pytest-cov/blob/HEAD/CHANGELOG.rst#630-2025-09-06) [Compare Source](https://redirect.github.com/pytest-dev/pytest-cov/compare/v6.2.1...v6.3.0) - 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`](https://redirect.github.com/pytest-dev/pytest-cov/blob/HEAD/CHANGELOG.rst#621-2025-06-12) [Compare Source](https://redirect.github.com/pytest-dev/pytest-cov/compare/v6.2.0...v6.2.1) - 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`](https://redirect.github.com/pytest-dev/pytest-cov/blob/HEAD/CHANGELOG.rst#620-2025-06-11) [Compare Source](https://redirect.github.com/pytest-dev/pytest-cov/compare/v6.1.1...v6.2.0) - 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`](https://redirect.github.com/pytest-dev/pytest-cov/blob/HEAD/CHANGELOG.rst#611-2025-04-05) [Compare Source](https://redirect.github.com/pytest-dev/pytest-cov/compare/v6.1.0...v6.1.1) - Fixed breakage that occurs when `--cov-context` and the `no_cover` marker are used together. ### [`v6.1.0`](https://redirect.github.com/pytest-dev/pytest-cov/blob/HEAD/CHANGELOG.rst#610-2025-04-01) [Compare Source](https://redirect.github.com/pytest-dev/pytest-cov/compare/v6.0.0...v6.1.0) - 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`](https://redirect.github.com/pytest-dev/pytest-cov/blob/HEAD/CHANGELOG.rst#600-2024-10-29) [Compare Source](https://redirect.github.com/pytest-dev/pytest-cov/compare/v5.0.0...v6.0.0) - 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. </details> --- ### 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](https://redirect.github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/canonical/craft-platforms). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xODguMiIsInVwZGF0ZWRJblZlciI6IjQ0LjE4OC4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJQUjogRGVwZW5kZW5jaWVzIl19-->

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b — closed stale Renovate PR to update pytest-check and pytest-cov was closed due to a uv.lock artifact update failure caused by a Python version conflict.

Update history

Date Change
closed
created

Related issues

Issue Project State Summary Similarity
#286 build(deps): update development dependencies (major versions) (main) (major) craft-platforms closed Renovate PR updating pytest-check to 3.0 and pytest-cov to 7.1 was closed due to a uv.lock resolution failure caused by a Python version constraint conflict (pytest-check 3.0 requires Python >=3.9).
98%
#292 build(deps): update development dependencies (major versions) (main) (major) craft-platforms open Renovate PR updating pytest-check from ~=2.3 to ~=3.0 and pytest-cov from ~=5.0 to ~=7.1 in dev dependencies. CI passing, awaiting review.
91%
#287 build(deps): update development dependencies (major versions) (main) (major) craft-platforms closed Dependency update PR closed due to `uv.lock` resolution failure; `pytest-check>=3.0` requires Python >=3.9, conflicting with the project's Python 3.8 support.
88%
#169 build(deps): update dependency pytest to v8 (main) craft-archives closed Closed unmerged after minimum-dependencies CI failed; Renovate stopped tracking pytest 8.x, later superseded by pytest 9 in #216 (2390cfc).
82%
#1053 build(deps): update dependency pytest-check to v2.8.0 (main) craft-application merged Renovate's pytest-check 2.8.0 update was merged into main via PR #1053 in commit 80d4b4b4.
82%
#185 build(deps): update dependency pytest-cov to v7 (main) craft-platforms closed Closed unmerged: pytest-cov 7 could not update uv.lock because it requires Python >=3.9 while craft-platforms still supports Python 3.8; identical PR #171 closed for the same conflict.
81%
#216 build(deps): update dependency pytest-cov to v7 imagecraft merged Renovate PR #216 was merged as commit a589bd8, updating pytest-cov from ~=6.0 to ~=7.0.
81%
#171 build(deps): update dependency pytest-cov to v7 craft-platforms closed Closed unmerged: pytest-cov 7 requires Python 3.9+, conflicting with craft-platforms' Python 3.8 support, so Renovate could not update uv.lock.
81%
#8 build(deps): update dependency pytest-cov to v6 craft-artifacts merged Renovate PR #8 merged into main as commit e93ac2c, bumping pytest-cov from ~=5.0 to ~=6.0 in pyproject.toml/uv.lock (Python 3.8 support dropped). Later superseded by PR #37 (pytest-cov v7, commit 0844ee2).
81%
#178 build(deps): update dependency pytest-mock to v3.14.1 (main) craft-archives closed pytest-mock 3.14.1 update PR #178 was closed unmerged after minimum-dependencies tests failed; Renovate then ignored that version. No resolving commit was recorded.
80%