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.5` → `~=3.0` |  |  | --- ### 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`. </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. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- 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-archives). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xODAuMCIsInVwZGF0ZWRJblZlciI6IjQ0LjE4MC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJQUjogRGVwZW5kZW5jaWVzIl19-->