Update deps #1
Open
Update deps #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. Thanks for integrating Codecov - We've got you covered ☂️ |
dartheian
force-pushed
the
update-deps
branch
2 times, most recently
from
6ce50da
to
f81bcdc
Compare
dartheian
force-pushed
the
update-deps
branch
3 times, most recently
from
319630e
to
bc9e5ac
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Python 3.6 has been deprecated. This PR removes it from the supported versions and adds Python 3.10 and 3.11 while updating some dependencies. A new formatted has been introduced: black. Also, pytest-freezegun has been removed due to inactivity and warnings with latest Python versions. GitHub actions have been changed to be triggered on all branches (not just master) in order to facilitate development.
I would suggest a test against the Satispay staging environment before merging. Probably a new activation code must be requested to the Satispay team since the last one may be expired.