chore(deps): update dependency pytest-randomly to v5

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
pytest-randomly (changelog)	>=4.1.0 → >=5.0.0

---

Release Notes

pytest-dev/pytest-randomly (pytest-randomly)

v5.0.0

Compare Source

• Support Python 3.15.

• Shuffle tests in a wrapper around the pytest_collection_modifyitems hook, guaranteeing that the shuffle runs before all other plugins’ implementations of the hook.

  Previously, pytest-randomly shuffled in a plain tryfirst hook implementation.
  When another plugin also implemented the hook with tryfirst, as pytest-django does, whichever plugin pytest happened to register later ran first.
  Registration order comes from package metadata on disk, which can differ between seemingly identical environments — even two containers built from the same Dockerfile, or the same virtual environment after reinstalling a package.
  As a result, the same seed could yield different test orders in different environments.
  Worse, in environments where pytest-randomly ended up shuffling last, it silently destroyed the other plugin’s ordering — for pytest-django, the grouping of database tests that mirrors Django’s test runner (non-transactional database tests, then transactional ones, then the rest).

  Now the shuffle always runs first, and plugins that group tests with a stable sort apply their grouping on top of the shuffled order, so the final order is reproducible from the seed alone.
  In environments that previously hit the reversed hook order, upgrading changes the test order for a given seed — restoring both reproducibility and other plugins’ grouping.

  PR #&#8203;746 <https://github.com/pytest-dev/pytest-randomly/pull/746>.
  Thanks to milssky for the report in Issue #&#8203;701 <https://github.com/pytest-dev/pytest-randomly/issues/701>.

• Require pytest 8+, the first version to require a version of pluggy that supports hook wrappers, as used by the above fix.

  PR #&#8203;746 <https://github.com/pytest-dev/pytest-randomly/pull/746>__.

• Reset Polyfactory <https://polyfactory.litestar.dev/>__\’s default random state at the start of every test, if it is installed.

  Thanks to Rahul Kumar in PR #&#8203;735 <https://github.com/pytest-dev/pytest-randomly/issues/735>__.

• Switch package build backend from setuptools to uv_build <https://docs.astral.sh/uv/concepts/build-backend/>__.
  This makes builds with uv about nine times faster, since uv runs the backend natively, without creating a build environment or spawning a Python process.
  Additionally, source distributions no longer include test files, which setuptools previously included incompletely, missing the files needed to actually run them.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Only on Sunday and Saturday (* * * * 0,6)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

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

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: rhel-lightspeed/coderabbit/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: ab5ad2ef-941d-4d7a-8f1d-aa6883c0e66e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}