build(deps-dev): bump pytest-rerunfailures from 16.4 to 16.5 in /prometheus in the all-dependencies group across 1 directory

[dependabot]

Bumps the all-dependencies group with 1 update in the /prometheus directory: pytest-rerunfailures.

Updates pytest-rerunfailures from 16.4 to 16.5

Changelog

Sourced from pytest-rerunfailures's changelog.

16.5 (2026-08-13)

Features ++++++++

• Add --max-suite-reruns option to cap the total number of reruns across the entire test suite. Once the limit is reached, no further reruns occur regardless of per-test --reruns or @pytest.mark.flaky settings. ([#298](https://github.com/pytest-dev/pytest-rerunfailures/issues/298) <https://github.com/pytest-dev/pytest-rerunfailures/issues/298>_)

Bug Fixes +++++++++

• Create a new test class instance for each rerun. Previously the instance of the failed attempt was reused, so state stored on self leaked into the rerun and broke test isolation. Fixtures cached at class scope or higher are still not re-executed. ([#268](https://github.com/pytest-dev/pytest-rerunfailures/issues/268) <https://github.com/pytest-dev/pytest-rerunfailures/issues/268>_)
• Prevent a rerun when a fixture teardown raises an error matching --rerun-except. Previously only the error from the current test stage was considered, so a --rerun-except-matching error raised during teardown was ignored and the test was rerun anyway. ([#270](https://github.com/pytest-dev/pytest-rerunfailures/issues/270) <https://github.com/pytest-dev/pytest-rerunfailures/issues/270>_)

Commits

• 88291f7 Preparing release 16.5
• 81141e0 Switch change log management to towncrier (#341)
• 6df6fb5 Create a fresh test class instance for each rerun (#340)
• 0440e21 fix: prevent rerun when teardown error matches --rerun-except (#338)
• 5fc2d79 feat: add --max-suite-reruns option to cap total reruns across suite (#332)
• 5fc495a Bump actions/setup-python from 6 to 7 in the actions group (#339)
• 1087cc2 Back to development: 16.5
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions