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 2.16.3, update changelog #8375

Conversation

Pierre-Sassoulas
Copy link
Member

No description provided.

@Pierre-Sassoulas Pierre-Sassoulas added the Maintenance Discussion or action around maintaining pylint or the dev workflow label Mar 3, 2023
@Pierre-Sassoulas Pierre-Sassoulas added this to the 2.16.3 milestone Mar 3, 2023
@codecov
Copy link

codecov bot commented Mar 3, 2023

Codecov Report

Merging #8375 (b5d6064) into maintenance/2.16.x (3dfa14f) will not change coverage.
The diff coverage is 100.00%.

Additional details and impacted files

Impacted file tree graph

@@                 Coverage Diff                 @@
##           maintenance/2.16.x    #8375   +/-   ##
===================================================
  Coverage               95.53%   95.53%           
===================================================
  Files                     177      177           
  Lines                   18642    18642           
===================================================
  Hits                    17810    17810           
  Misses                    832      832           
Impacted Files Coverage Δ
pylint/__pkginfo__.py 100.00% <100.00%> (ø)

@Pierre-Sassoulas Pierre-Sassoulas enabled auto-merge (squash) March 3, 2023 10:24
@Pierre-Sassoulas Pierre-Sassoulas merged commit 08bac36 into pylint-dev:maintenance/2.16.x Mar 3, 2023
@Pierre-Sassoulas Pierre-Sassoulas deleted the release-branch-2.16.3 branch March 3, 2023 10:24
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.

None yet

1 participant