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

Bump pytest from 5.2.2 to 5.2.4 #46

Merged
merged 1 commit into from
Nov 19, 2019
Merged

Conversation

dependabot-preview[bot]
Copy link
Contributor

@dependabot-preview dependabot-preview bot commented Nov 18, 2019

⚠️ Dependabot is rebasing this PR ⚠️

If you make any changes to it yourself then they will take precedence over the rebase.


Bumps pytest from 5.2.2 to 5.2.4.

Release notes

Sourced from pytest's releases.

5.2.4

pytest 5.2.4 (2019-11-15)

Bug Fixes

  • #6194: Fix
    incorrect discovery of non-test __init__.py files.
  • #6197: Revert
    "The first test in a package (__init__.py) marked with
    @pytest.mark.skip is now correctly skipped.".

5.2.3

pytest 5.2.3 (2019-11-14)

Bug Fixes

  • #5830: The
    first test in a package (__init__.py) marked with
    @pytest.mark.skip is now correctly skipped.
  • #6099: Fix
    --trace when used with parametrized functions.
  • #6183: Using
    request as a parameter name in @pytest.mark.parametrize now
    produces a more user-friendly error.
Changelog

Sourced from pytest's changelog.

pytest 5.2.4 (2019-11-15)

Bug Fixes

  • #6194: Fix incorrect discovery of non-test __init__.py files.
  • #6197: Revert "The first test in a package (__init__.py) marked with @pytest.mark.skip is now correctly skipped.".

pytest 5.2.3 (2019-11-14)

Bug Fixes

  • #5830: The first test in a package (__init__.py) marked with @pytest.mark.skip is now correctly skipped.
  • #6099: Fix --trace when used with parametrized functions.
  • #6183: Using request as a parameter name in @pytest.mark.parametrize now produces a more user-friendly error.
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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Bumps [pytest](https://github.com/pytest-dev/pytest) from 5.2.2 to 5.2.4.
- [Release notes](https://github.com/pytest-dev/pytest/releases)
- [Changelog](https://github.com/pytest-dev/pytest/blob/master/CHANGELOG.rst)
- [Commits](pytest-dev/pytest@5.2.2...5.2.4)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Nov 18, 2019
@sonic182 sonic182 merged commit c8c8ab2 into master Nov 19, 2019
@sonic182 sonic182 deleted the dependabot/pip/pytest-5.2.4 branch November 19, 2019 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant