#brettski
restive temple
nocturne harbor
As far as I know, there shouldn't need to be a new major version of stripe-node every time there is a new Stripe API version. The last two major versions were to address changes from the new API versions but before then there aren't many major version changes that came from a Stripe API version update
rigid lynx
I am not worried about the nodejs major version change, it's the API version changes which are killing us. Is the cadence of API version changes going to continue to be on this increased cadence?
nocturne harbor
Not sure, will see if we have anything on this. It is my understanding that the 2020-08-27 version lasted unusually long before we released another version, but I don't know if we have a specific cadence that we aim for in releasing new API versions
Can I ask what problems these upgrades are causing? I appreciate trying to stay on top of new versions but we do try to make that optional until it is the right time for you to upgrade
rigid lynx
In the last API release (in August) it removed the ability to set the description on a product during checkout. We heavily relied on this so we had our product descriptions in one place, our database.
We will need to refactor our code (which wont be too bad) but will not have to verify product descriptions in multiple places which will bite us at some point.
We run developer conferences and reuse the products between events to keep our administration down.
nocturne harbor
Gotcha. Unfortunately I'm not finding a preferred cadence that we have with these changes. We do generally try to make breaking changes that would require a new API version. But I am having trouble finding something that might help you get a better idea of how often this might happen
rigid lynx
And of course now there are changes like this:
Remove charges field on PaymentIntent and replace it with latest_charge. (#1614 )
Which we have to hunt through our code base and find and update. I hope there are really good reasons for such renames.
nocturne harbor
For that one I think it was to generally increase performance of payment intent endpoints. Just providing the one ID can be a lot easier to do at scale than having to render the list of objects.
Though that might not be the full story. We definitely take API changes, especially breaking ones, very seriously. There is a lot of review and debate before any changes are made
rigid lynx
Well it makes sense as we are only grabbing the first one as I assume most others are as well.
One last question.
The latest nodejs lib (11.1.0) should work fine with api version 2020-08-27? I don't know how many api versions back the library will support.
nocturne harbor
Yes it should work as far as I know. You can always pass whichever version for calls from the node library and I'm not seeing anything in the changelog that looks like it would break the ability to work with objects from 2020-08-27
rigid lynx
Thank you.