Update OpenAPI #83
Merged
Update OpenAPI #83
Conversation
This file contains hidden or 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
|
Welp, it looks like this will be my forcing function for getting fixtures in for the new deleted objects. |
It seems that I regressed payment intents during the last release (I think something wasn't committed). Here we update OpenAPI again to make sure that we have everything.
brandur-stripe
force-pushed
the
brandur-update-openapi-5
branch
from
4a50e4f to
b7951ed
Compare
Alright, they're now in! |
|
Released as 0.20.1. |
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.
It seems that I regressed payment intents during the last release (I
think something wasn't committed). Here we update OpenAPI again to make
sure that we have everything.