⬆️ deps: Update Python dev dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
pytest-rerunfailures	>=16.6 → >=16.6.1
ruff (source, changelog)	>=0.16.5 → >=0.16.6
ty (changelog)	>=0.0.77 → >=0.0.78

---

Release Notes

pytest-dev/pytest-rerunfailures (pytest-rerunfailures)

v16.6.1

Compare Source

Bug Fixes
+++++++++

• Ensure teardown reports are passed to pytest_runtest_logreport for rerun
  attempts. (#&#8203;237 <https://github.com/pytest-dev/pytest-rerunfailures/issues/237>_)
• Prevent superseded built-in subtest failures from remaining in the final test
  result when rerunning tests with pytest-xdist. (#&#8203;350 <https://github.com/pytest-dev/pytest-rerunfailures/issues/350>_)
• Restore module, class, and session scoped fixture teardown when a flaky
  marker condition is falsy. (#&#8203;351 <https://github.com/pytest-dev/pytest-rerunfailures/issues/351>_)
• Restore module, class, and session scoped fixture teardown when an error
  raised during teardown rules out a re-run. (#&#8203;356 <https://github.com/pytest-dev/pytest-rerunfailures/issues/356>_)
• Keep module, class, and session scoped fixtures alive across re-runs of a
  test whose call phase failed through subtests only. (#&#8203;357 <https://github.com/pytest-dev/pytest-rerunfailures/issues/357>_)
• Authenticate xdist StatusDB connections with a per-session token. (#&#8203;358 <https://github.com/pytest-dev/pytest-rerunfailures/issues/358>_)
• Ensure negative rerun counts do not skip the initial test execution. (#&#8203;359 <https://github.com/pytest-dev/pytest-rerunfailures/issues/359>_)

Misc
++++

• Replace deprecated Config.getvalue() calls with Config.getoption().
  (#&#8203;345 <https://github.com/pytest-dev/pytest-rerunfailures/issues/345>_)

astral-sh/ruff (ruff)

v0.16.6

Compare Source

Released on 2026-09-03.

Preview features

• Move pytest-fixture-autouse to the restriction category (#​28219)
• [flake8-pytest-style] Add an autofix for PT020 (#​27993)
• [flake8-tidy-imports] Prevent fix loop between TID254 and TID255 (#​28262)
• [isort] Exclude pragma comments from line length calculation (I001) (#​27313)

Bug fixes

• Validate unary expressions when parsing (#​28233)
• [flake8-async, pylint] Recognize builtins.open (ASYNC230, PLW1514) (#​28021)
• [flake8-bugbear] Fix panic on match subjects (B031) (#​27781)
• [flake8-datetimez] Reject tzinfo=None for datetime bounds (DTZ901) (#​28022)
• [flake8-pytest-style] Avoid duplicate PT017 diagnostics (#​27918)
• [ruff] Remove lint.external hint for Ruff-specific suppressions (RUF102) (#​27923)

Rule changes

• [flake8-use-pathlib] Add display-only fix for os.listdir (PTH208) (#​28027)

Documentation

• Add another example and glob reference for lint.per-file-ignores (#​28106)
• Add duplicate work guidance (#​28229)
• [flake8-async] Document thread offloading (ASYNC240) (#​28008)
• [pyupgrade] Clarify default encoding argument handling (UP012) (#​27315)

Other changes

• Allow unary plus in match patterns on Python 3.15 (#​28231)

Contributors

• @​flying-sheep
• @​pikammmmm
• @​fly1d
• @​waterWang
• @​Pierre-Sassoulas
• @​ntBre
• @​jelle-openai
• @​ericbuehl
• @​tjkuson
• @​AbhinavMir
• @​Whning0513
• @​chirizxc

astral-sh/ty (ty)

v0.0.78

Compare Source

Released on 2026-09-02.

Bug fixes

• Defer decorator-call diagnostics to avoid recursive-default cycles (#​28226)
• Make cyclic intersection simplification deterministic (#​28156)
• Stabilize cyclic terminal-call reachability (#​28216)

Preview features

• Refresh uv workspace metadata when dependencies change (#​28224)

Diagnostics

• Add a new disjoint-cast rule (#​28129)
• Report deprecated property accessors on intersections (#​28250)
• Report deprecations for implicit constructor calls (#​28251)
• Report deprecations for overloads, operators, and properties (#​28134)
• Respect overload selection in deprecation diagnostics (#​28148)

Core type checking

• Fix negative narrowing for protocols with gradual members (#​28198)
• Preserve ParamSpec bindings inferred against type context (#​28084)
• Preserve generic protocol materialization relations (#​28246)
• Preserve uncertain branches during quantification (#​28211)
• Respect type variables in top/bottom materializations of invariant generics (#​28072)
• Sync vendored typeshed stubs (#​28217). Typeshed diff
• Treat captured bound-method receivers covariantly (#​28180)
• Unsound intersection simplification for generic iterables (#​28068)
• Validate type variable scopes in constructors and aliases (#​28130)
• lambda functions are always truthy (#​28254)

Performance

• Optimize materialized recursive protocol comparisons (#​28079)
• Optimize recursive protocol checks for nested type variables (#​28257)

Contributors

• @​charliermarsh
• @​sharkdp
• @​zsol
• @​AlexWaygood
• @​ibraheemdev
• @​carljm

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pyproject.toml

Artifact update for ty resolved to version 0.0.79, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 0.0.78
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/