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 pylint-pytest from 1.1.2 to 1.1.5 #147

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Nov 20, 2023

Bumps pylint-pytest from 1.1.2 to 1.1.5.

Release notes

Sourced from pylint-pytest's releases.

v1.1.5

This is Release v1.1.5, released on 2023-11-06

What's Changed

Full Changelog:

v1.1.4

This is Release v1.1.4, released on 2023-11-06

What's Changed

New Contributors

Full Changelog:

v1.1.3

This is Release v1.1.3, released on 2023-10-23

[1.1.3] - 2023-10-23

This is the first release after maintenance was assumed by https://github.com/stdedos.

The focus of this release was to improve automation:

  • Fix the continuous integration,
  • Run tests as part of branches and PRs,
  • Use .pre-commit-config.yaml file to upkeep the code quality, and
  • Automate the release process

There should be no functional changes in this release, although there are changes in the source code.

A heartfelt thank you to https://github.com/Pierre-Sassoulas for his invaluable contributions to the continued maintenance of this project!

Fixed

  • The continuous integration was fixed, as a new maintenance team was assembled.

Added

... (truncated)

Changelog

Sourced from pylint-pytest's changelog.

[1.1.5] - 2023-11-13

This is a small bugfix release.

Fixed

[1.1.4] - 2023-11-06

This is a small bugfix release.

Fixed

  • anis-campos/fix_is_pytest_fixture (pylint-dev/pylint-pytest#2) Astroid has different semantics when using import pytest or from pytest import ..., which affects the detection of pytest fixtures.

Improved

  • pre-commit: (pylint-dev/pylint-pytest#20)
    • Added more checks to the pre-commit hook.
      repos:
        - repo: https://github.com/pre-commit/pre-commit-hooks
          hooks:
          - id: check-yaml
          - id: check-toml
          - id: check-vcs-permalinks
          - id: check-shebang-scripts-are-executable
          - id: name-tests-test
        - repo: https://github.com/jumanjihouse/pre-commit-hook-yamlfmt
            - id: yamlfmt
        - repo: local
          hooks:
            - id: python-no-log-fatal
              name: avoid logger.fatal(
    • Unified formatting (always expanded arrays; not covered by linters, sadly)

[1.1.3] - 2023-10-23

This is the first release after maintenance was assumed by https://github.com/stdedos.

The focus of this release was to improve automation:

  • Fix the continuous integration,
  • Run tests as part of branches and PRs,
  • Use .pre-commit-config.yaml file to upkeep the code quality, and

... (truncated)

Commits
  • c84ad36 Release v1.1.5
  • 3cee43d Merge pull request #25 from stdedos/ci/fix-windows-artifacts-slugification
  • a4245b1 Merge branch 'master' into ci/fix-windows-artifacts-slugification
  • e29fe48 Merge pull request #26 from stdedos/test/improve_coverage+setup+docs
  • d8db8e4 Improve copy-paste docstring from 8756cc4627a66f150197519a2588512511f0c4f3
  • 8edad60 Fix tests running via PyCharm
  • 90e4141 Move --cov-report=html to addopts
  • d11811e Windows Artifacts have incorrect Slugification
  • c1547d9 Merge pull request #21 from stdedos/replay/fix/nate/better-unused-argument
  • bb6af8d Merge branch 'master' into replay/fix/nate/better-unused-argument
  • Additional commits viewable in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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)

Bumps [pylint-pytest](https://github.com/pylint-dev/pylint-pytest) from 1.1.2 to 1.1.5.
- [Release notes](https://github.com/pylint-dev/pylint-pytest/releases)
- [Changelog](https://github.com/pylint-dev/pylint-pytest/blob/master/CHANGELOG.md)
- [Commits](pylint-dev/pylint-pytest@pylint-pytest-1.1.2...v1.1.5)

---
updated-dependencies:
- dependency-name: pylint-pytest
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Copy link
Contributor Author

dependabot bot commented on behalf of github Nov 27, 2023

Superseded by #149.

@dependabot dependabot bot closed this Nov 27, 2023
@dependabot dependabot bot deleted the dependabot/pip/pylint-pytest-1.1.5 branch November 27, 2023 01:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants