Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): bump pytest-rerunfailures from 11.1.2 to 12.0 in /requirements #1054

Merged
merged 3 commits into from
Jul 12, 2023

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 10, 2023

Bumps pytest-rerunfailures from 11.1.2 to 12.0.

Changelog

Sourced from pytest-rerunfailures's changelog.

12.0 (2023-07-05)

Breaking changes ++++++++++++++++

  • Drop support for pytest < 6.2.

Features ++++++++

  • Add only_rerun and rerun_except arguments to @pytest.mark.flaky marker.

  • Add support for pytest 7.3, 7.4.

Bug fixes +++++++++

  • Failures are now rerun only if they match at least one --only-rerun pattern (if given) and none of the --rerun-except patterns. Previously, using both --only-rerun and --rerun-except together could cause failures to be rerun even if they did not match any --only-rerun pattern, and when using multiple --rerun-except patterns, all failures would be rerun unless they matched every pattern. ([#225](https://github.com/pytest-dev/pytest-rerunfailures/issues/225) <https://github.com/pytest-dev/pytest-rerunfailures/issues/225>_)
Commits

Dependabot compatibility score

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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

📚 Documentation preview 📚: https://lightning-bolts--1054.org.readthedocs.build/en/1054/

Bumps [pytest-rerunfailures](https://github.com/pytest-dev/pytest-rerunfailures) from 11.1.2 to 12.0.
- [Changelog](https://github.com/pytest-dev/pytest-rerunfailures/blob/master/CHANGES.rst)
- [Commits](pytest-dev/pytest-rerunfailures@11.1.2...12.0)

---
updated-dependencies:
- dependency-name: pytest-rerunfailures
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the ci/cd Continues Integration and delivery label Jul 10, 2023
@dependabot dependabot bot requested a review from a team July 10, 2023 12:00
@Borda Borda enabled auto-merge (squash) July 10, 2023 12:48
@mergify mergify bot added the ready label Jul 10, 2023
@Borda Borda merged commit 4f910f6 into master Jul 12, 2023
28 of 29 checks passed
@Borda Borda deleted the dependabot-pip-requirements-pytest-rerunfailures-12.0 branch July 12, 2023 21:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci/cd Continues Integration and delivery ready
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant