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

Upgrade to dj-stripe 1.1.1 #1

Open
wants to merge 51 commits into
base: master
Choose a base branch
from

Conversation

AndrewSpeed
Copy link

What changed?

As part of the process to upgrade dj-stripe to it's latest version, we'll need to migrate to version 1.1.x first, as 1.2.0 resets the dj-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 to 1.2.0 while maintaining our additional commit which fixes webhook atomicity, which gets addressed in the main repository in version 2.0.3.

Fixes a test error on Django master

Refs. django/django@b3cffde
This allows using a different API base host for development purposes.
For example: https://github.com/stripe/stripe-mock
kavdev and others added 21 commits May 29, 2018 15:07
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
Backwards-incompatible changes and deprecations
-----------------------------------------------

Removal of polymorphic models

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?

Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

6 participants