Auto-merge forward rel-10.7 → dev

docs/en/release-info/migration-guides/abp-10-2.md

@@ -126,7 +126,15 @@ ABP now uses Angular's ARIA support for accessible tabs. Add the `@angular/aria`
 
 ## Pro
 
-There are no breaking changes on the PRO side. However, please check the following sections if they apply to your application.
+This version contains the following changes on the PRO side:
+
+### ABP Suite Many-to-Many Regeneration
+
+ABP Suite v10.2 changed the generated names for many-to-many join artifacts from the related entity name to the navigation collection name. For example, a `Categories` navigation collection now uses `BookCategories`, `AddToCategories` / `RemoveFromCategories`, and the `AppBookCategories` table instead of `BookCategory`, `AddCategory` / `RemoveCategory`, and `AppBookCategory`. This allows multiple many-to-many relations to the same entity to have distinct generated names.
+
+Entities generated before v10.2 keep the previous names in their source code. Regenerating one of these entities with ABP Suite v10.2 through v10.6 may change its join entity, collection methods, and EF Core table mapping. EF Core may then scaffold the table change as `DropTable` followed by `CreateTable`, which removes the existing relationship data when the migration is applied.
+
+ABP Suite v10.7 and later detect and preserve the existing naming convention during regeneration. Upgrade the solution and ABP Suite together before regenerating these entities. If the solution must remain on v10.2 through v10.6, preserve the previous relationship names and table mappings from source control, remove the newly generated join entity files, and recreate the migration. Do not apply the migration if it drops and recreates an existing join table.
 
 ### Add `@volo/ai-management` NPM Package for MVC UI