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 to 3.0.4, update changelog #9458

Conversation

Pierre-Sassoulas
Copy link
Member

What's new in Pylint 3.0.4?

Release date: 2024-02-23

False Positives Fixed

Other Bug Fixes

@Pierre-Sassoulas Pierre-Sassoulas added the Maintenance Discussion or action around maintaining pylint or the dev workflow label Feb 23, 2024
@Pierre-Sassoulas Pierre-Sassoulas added this to the 3.0.4 milestone Feb 23, 2024
Copy link

codecov bot commented Feb 23, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.78%. Comparing base (327785d) to head (b80d7aa).

Additional details and impacted files

Impacted file tree graph

@@                Coverage Diff                 @@
##           maintenance/3.0.x    #9458   +/-   ##
==================================================
  Coverage              95.78%   95.78%           
==================================================
  Files                    173      173           
  Lines                  18704    18704           
==================================================
  Hits                   17916    17916           
  Misses                   788      788           
Files Coverage Δ
pylint/__pkginfo__.py 100.00% <100.00%> (ø)

@Pierre-Sassoulas Pierre-Sassoulas merged commit 8115381 into pylint-dev:maintenance/3.0.x Feb 23, 2024
24 checks passed
@Pierre-Sassoulas Pierre-Sassoulas deleted the release-branch-3.0.4 branch February 23, 2024 20:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Maintenance Discussion or action around maintaining pylint or the dev workflow
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants