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

Update pylint and pylint-django #394

Merged
merged 1 commit into from
Aug 22, 2020
Merged

Conversation

ajhodges
Copy link
Contributor

Description

  • Update pylint 2.5.2 -> 2.5.3
  • Update pylint-django 2.0.15 -> 2.2.0

Related Issue

#393

Motivation and Context

Bumps dependency versions

How Has This Been Tested?

Passes local tox, also tested (installed via git hash) with our open source projects

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • My change requires a change to the dependencies
  • I have updated the dependencies accordingly
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 80.626% when pulling 72e9b88 on ShipChain:develop into e6bb8a3 on PyCQA:develop.

Copy link
Contributor

@chocoelho chocoelho left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
thanks @ajhodges

@chocoelho chocoelho merged commit af2b78b into prospector-dev:develop Aug 22, 2020
@chocoelho chocoelho mentioned this pull request Aug 30, 2020
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.

3 participants