You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Hi,
I created stripe account recently and cannot go further back than version 2022-11-15, which is the version that broke Charges ( #347 ). And because you cannot specify api version when testing webhooks locally , i get errors.
Describe the solution you'd like
Migrate version to 2023-10-16 (or at least 2022-11-15)
Describe alternatives you've considered
No response
Additional context
Is there any timeline to this feature? Is this even being considered? If no, why not?
The text was updated successfully, but these errors were encountered:
Same, so I am using async-stripe for all my calls, but wrote my own webhook code. It's not pretty or in publishable state, but it sounds like there might be a need so I'll see if I can clean it up and decouple it
I didn't fully realize that CI was always pulling latest stripe version from their repo, because the README in this repo is outdated:
"The latest supported version of the Stripe API is 2020-08-27...."
This library always tracks the most recent version so if there are errors it is likely due to issues in the stripe openapi definitions. Are you also encountering deserialization issues when processing charges?
@arlyon just found your comment after creating an issue also related to deserializing charges. Glad to see it's on your radar. Let me know if I can help out!
Is your feature request related to a problem? Please describe.
Hi,
I created stripe account recently and cannot go further back than version 2022-11-15, which is the version that broke Charges ( #347 ). And because you cannot specify api version when testing webhooks locally , i get errors.
Describe the solution you'd like
Migrate version to 2023-10-16 (or at least 2022-11-15)
Describe alternatives you've considered
No response
Additional context
Is there any timeline to this feature? Is this even being considered? If no, why not?
The text was updated successfully, but these errors were encountered: