#alex-from-fuxam_api
wintry mangoBOT
đ 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/1366427794875224147
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
livid garnet
That latest version had significant breaking changes
It's not recommended to upgrade unless you tested thoroughly in test mode first
And thoroughly read the changelog to understand the changes
- Is there anything I need to do in order to make sure my production environment also starts using the new stripe objects?
Not sure I understand what you mean by this exactly. Upgrading your api version will ensure new object shapes are used when using the api with this new version.
- Where do I get updates if I need to update my code so significantly?
I don't understand this question.
- How is my production code affected by this? will it still get updates according to the previous api version?
If you changed your api version, everything will be affected. It's a significant change with many breaking changes.
- Invoice objects used to have a subscription id. Where can I find that now?
This is covered in the aforementioned changelog: https://docs.stripe.com/changelog/basil/2025-03-31/adds-new-parent-field-to-invoicing-objects . It's now within parent