From 8af63bc3db5746ec23965e5043390a84a63f55a5 Mon Sep 17 00:00:00 2001 From: maliming Date: Tue, 16 Sep 2025 16:55:19 +0800 Subject: [PATCH] Update ABP 10.0 migration guide for OpenIddict and Mapperly --- docs/en/release-info/migration-guides/abp-10-0.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/en/release-info/migration-guides/abp-10-0.md b/docs/en/release-info/migration-guides/abp-10-0.md index 65c1be1d82..4fa4fefe6a 100644 --- a/docs/en/release-info/migration-guides/abp-10-0.md +++ b/docs/en/release-info/migration-guides/abp-10-0.md @@ -51,6 +51,18 @@ M((array, num) => Enumerable.Contains(array, num)); // ok, binds to Enumerable.C See the [C# 14 overload resolution with span parameters](https://learn.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/10.0/csharp-overload-resolution#recommended-action) for more information. +### OpenIddict 7.X + +We upgraded OpenIddict to 7.X. See the [OpenIddict 6.x to 7.x Migration Guide](https://documentation.openiddict.com/guides/migration/60-to-70.html) for more information. + +OpenIddict 7.X changed the `OpenIddictToken` entity, you must create a new database migration if you use Entity Framework Core. + +### Migrating from AutoMapper to Mapperly + +The AutoMapper library is no longer free for commercial use. For more details, you can refer to this [announcement post](https://www.jimmybogard.com/automapper-and-mediatr-going-commercial/). + +In this version, all ABP modules use Mapperly instead of AutoMapper. ABP Framework provides both AutoMapper and Mapperly integrations. If your project currently uses AutoMapper and you don't have a commercial license, you can follow the [Migrating from AutoMapper to Mapperly](https://github.com/abpframework/abp/blob/dev/docs/en/release-info/migration-guides/AutoMapper-To-Mapperly.md) document to migrate to Mapperly. + ### Failure Retry Policy for InboxProcessor We added a failure retry policy to `AbpEventBusBoxesOptions` (see `InboxProcessorFailurePolicy` and `InboxProcessorRetryBackoffFactor`). Because this change adds and removes fields in the `IncomingEventRecord` entity, you must create a new database migration if you use Inbox/Outbox with Entity Framework Core.