Upgrading From 3.23 To 3.24
Removal of Authorize.net Plugin​
The legacy Authorize.net payment gateway plugin has been removed from Saleor core in 3.24 (see saleor/saleor#19142).
Before upgrading to 3.24, stop using the Authorize.net plugin. After the upgrade, any checkout or order flow still relying on it will fail because the gateway is no longer registered.
Migration steps​
- Stop using the plugin before upgrading. Disable Authorize.net as an active payment method in all channels that reference it, and confirm no in-flight checkouts depend on it.
- Migrate to another payment gateway. Saleor recommends integrating a Payment App instead — see the Payment Apps overview and How to Build a Payment App for guidance. Existing options include the Stripe App or any third-party Payment App from the App Store.
Prohibited MANAGE_APPS permission for Apps​
Prior to Saleor 3.24, MANAGE_APPS permission was technically allowed for Apps, but it shouldn't be. That was not a significant issue because Saleor was not allowing Apps to consume this permission in any way.
However, MANAGE_APPS is reserved for a staff user. Saleor 3.24 locks possibility to create/install app with this permission. Now all installations will be rejected.
During the upgrade, all apps with MANAGE_APPS permission will be updated and the permission will be removed.
All apps that somehow remained with MANAGE_APPS (e.g. migration not yet over, or a bug) will reject to issue a token.
Migration steps​
If none of your apps have MANAGE_APPS permission, you can skip this step. Otherwise, Saleor during the upgrade will automatically remove MANAGE_APPS permission from all the apps.
If you want to test if everything works as expected, you can manually remove this permission before the upgrade and prepare your apps for 3.24:
- Ensure your apps (manifests) don't have
MANAGE_APPSpermission. Such installation will be rejected after the upgrade. - Manually update apps (
appUpdatemutation) to removeMANAGE_APPSpermission and test if they work while still on 3.23.