Skip to content

[Backport maintenance/3.3.x] Bump astroid from 3.3.5 to 3.3.8 (#10125) #10155

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

Conversation

jacobtylerwalls
Copy link
Member

(cherry picked from commit 31e7674)

@jacobtylerwalls jacobtylerwalls added this to the 3.3.3 milestone Dec 24, 2024
@jacobtylerwalls jacobtylerwalls changed the title Bump astroid from 3.3.5 to 3.3.8 (#10125) [Backport maintenance/3.3.x] Bump astroid from 3.3.5 to 3.3.8 (#10125) Dec 24, 2024
Copy link

codecov bot commented Dec 24, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.81%. Comparing base (2287797) to head (58324cc).
Report is 177 commits behind head on maintenance/3.3.x.

Additional details and impacted files

Impacted file tree graph

@@                  Coverage Diff                  @@
##           maintenance/3.3.x   #10155      +/-   ##
=====================================================
- Coverage              95.85%   95.81%   -0.05%     
=====================================================
  Files                    174      174              
  Lines                  18873    18954      +81     
=====================================================
+ Hits                   18090    18160      +70     
- Misses                   783      794      +11     

see 5 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@jacobtylerwalls jacobtylerwalls merged commit 1f9b947 into pylint-dev:maintenance/3.3.x Dec 24, 2024
23 checks passed
@jacobtylerwalls jacobtylerwalls deleted the backport-10125-to-maintenance/3.3.x branch December 24, 2024 02:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant