#inforandre_code
hasty juniperBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1413448806556500070
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
tranquil basalt
Hmm, shouldn't be any incompatability per se. Just means that requests initialised by Stripe.js will use a .acacia version
analog crater
I guess we can assume that each SDK can be updated independently? Perhaps even bump stripe-js to basil while BE is on V3 ?
And regarding the API version on the dashboard? Should we update that last?
tranquil basalt
I guess we can assume that each SDK can be updated independently? Perhaps even b...
Sure, you just need to be aware that request response shapes may differ due to the API versioning difference
tranquil basalt
And regarding the API version on the dashboard? Should we update that last?
The account API version is mostly redundant in regards to API requests if you're using our SDKs as they set the API version in the headers for each request according to the version they're pinned to
It's only really relevant for webhooks
dusk orbit
👋
I work with @analog crater
We're thinking of leaving the webhooks upgrade for last
At the moment we're already on different versions for the client SDK (Our BE => to Stripe) and the WEbhooks
So to confirm its fine that we:
- Bump the stripejs version
- Bump our BE Go SDK version for the requests
- Follow the Webhook upgrade migration guide (at this point both our client and webhook handler would be at the same version upgrade)
- Finally bump that setting on the Dashboard
?
tranquil basalt
Yeah that seems logical. There's nothing here that will be directly incompatible, you just need to understand that the API response shapes/payloads will differ so ensure your integration can handle that