[WIP] updates for upcoming Stripe API version bump #1068
Closed
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
|
Nice! Thanks Jeremy, and let us know if you need any other support here. |
ob-stripe
changed the title
jhoon-stripe
force-pushed
the
jhoon-plan-and-product-updates
branch
from
da370d6
to
c0eea9d
Compare
|
Should close this PR in favor of: #1099 |
|
Yup, thanks @pantera-stripe! |
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.
Summary
Similar to stripe/stripe-go#496, this PR adds support for an upcoming Stripe API version, tentatively dated 2017-12-01.
Testing
I'll plan to...
cc @stripe/api-libraries