search

pylint-dev / pylint-pytest

A Pylint plugin to suppress pytest-related false positives.
https://pypi.org/project/pylint-pytest/
MIT License
14 stars 3 forks source link

Release v1.1.3rc0 #17

Closed stdedos closed 10 months ago

stdedos commented 10 months ago

Additionally, fixes https://github.com/pylint-dev/pylint-pytest/issues/13

Signed-off-by: Stavros Ntentos 133706+stdedos@users.noreply.github.com

codecov[bot] commented 10 months ago

Codecov Report

All modified lines are covered by tests :white_check_mark:

Comparison is base (f8da197) 91.24% compared to head (4298cc7) 91.24%.

Additional details and impacted files ```diff @@ Coverage Diff @@ ## master #17 +/- ## ======================================= Coverage 91.24% 91.24% ======================================= Files 18 18 Lines 514 514 Branches 97 97 ======================================= Hits 469 469 Misses 33 33 Partials 12 12 ``` | [Flag](https://app.codecov.io/gh/pylint-dev/pylint-pytest/pull/17/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pylint-dev) | Coverage Δ | | |---|---|---| | [3.10](https://app.codecov.io/gh/pylint-dev/pylint-pytest/pull/17/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pylint-dev) | `91.05% <ø> (ø)` | | | [3.11](https://app.codecov.io/gh/pylint-dev/pylint-pytest/pull/17/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pylint-dev) | `91.05% <ø> (ø)` | | | [3.6](https://app.codecov.io/gh/pylint-dev/pylint-pytest/pull/17/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pylint-dev) | `91.05% <ø> (ø)` | | | [3.7](https://app.codecov.io/gh/pylint-dev/pylint-pytest/pull/17/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pylint-dev) | `91.05% <ø> (ø)` | | | [3.8](https://app.codecov.io/gh/pylint-dev/pylint-pytest/pull/17/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pylint-dev) | `91.05% <ø> (ø)` | | | [3.9](https://app.codecov.io/gh/pylint-dev/pylint-pytest/pull/17/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pylint-dev) | `91.05% <ø> (ø)` | | | [macos-latest](https://app.codecov.io/gh/pylint-dev/pylint-pytest/pull/17/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pylint-dev) | `91.05% <ø> (ø)` | | | [ubuntu-20.04](https://app.codecov.io/gh/pylint-dev/pylint-pytest/pull/17/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pylint-dev) | `91.05% <ø> (ø)` | | | [ubuntu-latest](https://app.codecov.io/gh/pylint-dev/pylint-pytest/pull/17/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pylint-dev) | `91.05% <ø> (ø)` | | | [windows-latest](https://app.codecov.io/gh/pylint-dev/pylint-pytest/pull/17/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pylint-dev) | `91.05% <ø> (ø)` | | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pylint-dev#carryforward-flags-in-the-pull-request-comment) to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

stdedos commented 10 months ago

Tests were verified manually to be passing (i.e., all show OK except py312)

stdedos commented 10 months ago

So ... how does it feel @Pierre-Sassoulas to release Friday at 11am? 😅

stdedos commented 10 months ago

I don't have any issues releasing on a Friday, especially when the current release is broken 😄

Well, define broken 😅

There are bugs. How serious/critical they are? Idk

Pierre-Sassoulas commented 10 months ago

I mean broken with pylint 3.0, a 1.1.3 release would prevent new install of pylint-pytest to upgrade to a pylint version it's not compatible with.

Pierre-Sassoulas commented 10 months ago

But yeah, it's possible to just add a pylint<3 in requirements for users.