-
Notifications
You must be signed in to change notification settings - Fork 0
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
Upgrade to dj-stripe 1.1.1 #1
base: master
Are you sure you want to change the base?
Conversation
….7.x"" This reverts commit c3a2e95.
Fixes a test error on Django master Refs. django/django@b3cffde
Django 2.2 compatibility Refs django/django@1e81a4b
This allows using a different API base host for development purposes. For example: https://github.com/stripe/stripe-mock
CLoses dj-stripe#534 Supercedes dj-stripe#594
Fixes issues on stripe>=2.0 (cherry picked from commit cf70c05)
Fixes issues on stripe>=2.0 (cherry picked from commit 23fec03)
Works around an issue in stripe-python 2.0 and pip. Context: stripe/stripe-python#447
9301d34
to
feb339d
Compare
Backwards-incompatible changes and deprecations | ||
----------------------------------------------- | ||
|
||
Removal of polymorphic models |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Flagging Backwards-incompatible
changes and deprecations for folks to easily spot it during the review.
Do we extend any of these models in any way?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, the only references to the stripe polymorphic models provided by djstripe.stripe_objects
that I could find were in documentation references in cloudsmith/core/billing/plans.py
What changed?
As part of the process to upgrade
dj-stripe
to it's latest version, we'll need to migrate to version1.1.x
first, as1.2.0
resets thedj-stripe
migration numbering.This PR updates our fork to version
1.1.1
so that we can run the necessary migrations on staging and production before migrating to1.2.0
while maintaining our additional commit which fixes webhook atomicity, which gets addressed in the main repository in version2.0.3
.