Django Admin breaks when upgrading to Django 5.2 without upgrading djstripe. See https://read-the-docs.sentry.io/issues/6575661535/

Note that we need to perform the upgrade in two steps: first to 2.7 and then to 2.8. See https://dj-stripe.dev/2.9/upgrade_dj_stripe/

Ideally, we should upgrade to the latest version.

I started following the djstripe guide:

Migrations

1. We have only 2 migrations that depend on djstripe migrations

readthedocs/organizations/migrations/0011_add_stripe_subscription_field.py
11:        ("djstripe", "0010_alter_customer_balance"),

readthedocs/organizations/migrations/0010_add_stripe_customer.py
11:        ("djstripe", "0010_alter_customer_balance"),

2. The latest version of djstripe (2.9.0) has the 0010_alter_customer_balance migration file

When running the migrations locally, I received this message, so we need to update the test keys:

?: (djstripe.I001) You don't have any API Keys in the database. Did you forget to add them?
	HINT: Add STRIPE_TEST_SECRET_KEY and STRIPE_LIVE_SECRET_KEY directly from the Django Admin.

It seems there is nothing we need to do related to the migrations.

Backward incompatibility changes

• In 2.9.0 deprecates DJSTRIPE_WEBHOOK_VALIDATION setting, which we are currently using. This needs to be configured through the admin when performing the migration.
• 2.9.0 removes DJSTRIPE_WEBHOOK_SECRET which we are using, but it doesn't say exactly what's the replacement. I understand this is done via the Django Admin now for each webhook.

I checked all release notes from 2.6.x to 2.9.x and I only found these affecting us.

The steps we should follow are described in #9688 (comment). I'm copying them here:

Run the migrations on web extra
Create an API key on the admin (/admin/djstripe/apikey/)
Release the webs
Create a webhook endpoint after the release is done (/admin/djstripe/webhookendpoint/), the webhook will be created on stripe automatically.
Deactivate the old webhook

The old and the new webhook will work at the same time, so we won't lose any events.

The migration is dj-stripe/dj-stripe//blob/bc0bd5c1/djstripe/migrations/0011_2_7.py, there are a couple of new fields that aren't nullable, but if the webhooks fail, stripe will retry them, and by that time the new code would be live.

I think we can target this for the next deploy.