How to opt into the new webhook API versions?

[echelon]

Hi folks, I have older businesses running on old webhook API versions with async-stripe successfully.

I just created a new Stripe organization, and the webhook version for new accounts is pinned at 2025-08-27.basil with no way to downgrade.

ApiVersion::V2023_10_16; is currently the latest version supported in main. When testing against events sent from 2025-08-27.basil, most of the core events we care about are broken. Payloads can't be rehydrated due to missing or changed fields.

What's the best way to roll forward? Pin our dependency against async-stripe branch next? Is this considered safe? If not, is there another alternative or another branch? A little more clarity in the README / docs for how to best roll forward would be helpful to folks bumping into this.

We obviously can't tell Stripe we want to use 2023-10-16, unfortunately.

Thanks for all the hard work on async-stripe !

Edit: I may have answered my own question. It looks like you have a github action that automatically ingests OpenAPI changes, performs codegen, then publishes a branch matching that version of the API. (eg. branch openapi-1752798979)

A few questions: Are these branches all generally safe to use? If they built red, should we avoid them? And why is main behind these?

Thanks again!

[arlyon]

Hi, sorry, did not get a notif for this.

The openapi-xxx branches are 'internal' and used during for the automated spec update PRs. At the time you asked this question, the advice was to use next but that has since merged so the new advice is to use the alpha release.