Bump pylint-pytest from 1.1.2 to 1.1.4

[dependabot]

Bumps pylint-pytest from 1.1.2 to 1.1.4.

Release notes

Sourced from pylint-pytest's releases.

v1.1.4

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

What's Changed

• fix is pytest fixture by @​anis-campos in pylint-dev/pylint-pytest#2
• MOAR pre-commit + README.md by @​stdedos in pylint-dev/pylint-pytest#20

New Contributors

• @​anis-campos made their first contribution in pylint-dev/pylint-pytest#2

Full Changelog:

• https://github.com/pylint-dev/pylint-pytest/blob/v1.1.4/CHANGELOG.md#114---2023-11-06
• pylint-dev/pylint-pytest@v1.1.3...v1.1.4

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

• Added an extensive .pre-commit-config.yaml file to upkeep the code quality. It includes, among others, black, mypy (in non-strict mode yet), ruff, and pylint.
• Added an automated release process

Changed

• Redirected all repository URLs to the https://github.com/pylint-dev/pylint-pytest.

Full Changelog: pylint-dev/pylint-pytest@pylint-pytest-1.1.2...v1.1.3

v1.1.3rc1

This is a Release Candidate for v1.1.3 - which will be released on Monday, 2023-10-23

On top of https://github.com/pylint-dev/pylint-pytest/releases/tag/v1.1.3rc0, we have:

... (truncated)

Changelog

Sourced from pylint-pytest's changelog.

[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
• 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.

... (truncated)

Commits

• 106c3b8 Release v1.1.4
• e73cc2f Merge pull request #20 from stdedos/ci/pre-commit/add-MOAR
• c3757aa MOAR pre-commit + README.md
• a5c6855 Merge pull request #2 from anis-campos/fix_is_pytest_fixture
• 0a47a49 Release v1.1.3
• d5cd873 Fixing _is_pytest_fixture
• 630172b test direct import
• cb653a0 Merge pull request #19 from stdedos/release/v1.1.3rc1
• 85dd457 Improve packaging + Release v1.1.3rc1
• 4971561 Release v1.1.3rc0 (#17)
• Additional commits viewable 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 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)

[dependabot]

Superseded by #147.