#cobra_florianw
cyan oakBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- cobra_florianw, 2 days ago, 18 messages
opaque thicket
You'll want to look through the changelog for the library you're updating to see if any changes might break your integration. Alternatively, you could create a development environment with a copy of the production code, then update the Nuget package and see if anything breaks (though there may be edge-cases you could miss, so this method should probably be used in tandem with reviewing the changelog)
https://github.com/stripe/stripe-dotnet/blob/master/CHANGELOG.md
mental schooner
We have a deployment set up where the code goes to a development environment, and after that to staging and later into production.
Both development and staging are using the test mode of stripe, not of the same account tho.
I tested all my changes in develop after update, there where no issues. I didn't however have any ongoing payments so i could not check those.
I'll check the changelog and see if anything in there could break our code. Otherwise i will roll back the changes on our staging environment for now.
mental schooner
I looked over the changelogs. It does seem like nothing would break our code. I will still communicate the issue with our PO to see what he would prefer.
Thank you for your help so far!
opaque thicket
Sure thing!
cyan oakBOT