Hello ABP Support Team,
We are preparing to upgrade our ABP Commercial Microservice solution from v9.3.1 (Angular ~9.3.2, SQL Server, Auth Server separated) to the latest stable ABP version, and we would appreciate your guidance so we can plan the upgrade safely and with minimal risk to our running environments.
Our solution is based on the ABP Microservice startup template and has evolved with customizations across backend services, Auth Server, gateways, and Angular applications (including shared libraries / Module Federation patterns). Before we proceed with the upgrade, we want to make sure we are following the recommended ABP approach for this template so we do not carry forward anything that could cause upgrade friction, regressions, or unnecessary rework.
Could you please help us with the following as part of upgrade readiness / best-practice guidance?
Confirm the recommended upgrade path from 9.3.x to the latest stable release for a Microservice + Angular + Auth Server Separated solution, including any required intermediate steps, breaking changes, and migration guides we should follow carefully.
Advise us on areas that commonly need attention during this upgrade (NuGet/NPM packages, ABP Studio/CLI, OpenIddict/Auth Server, Angular packages & LeptonX, EF Core migrations, distributed events/inbox-outbox, background jobs, permissions, and multi-tenancy), and what we should validate in a non-production environment first.
Based on a high-level review of our solution structure and key customizations (we can share the repository / relevant modules privately), please highlight any places where we may have drifted from the recommended ABP Microservice patterns/conventions across layers (domain/application, EF Core, HTTP APIs, Auth Server, Angular, and shared contracts). Our goal is simply to know if anything should be corrected before or during the upgrade so we stay aligned with ABP’s supported design and avoid upgrade blockers.
Please share a practical upgrade checklist for our architecture so we can execute the upgrade without impacting production (staging first, package update order, DB migration strategy, Auth Server/token compatibility, Angular rebuild/proxy regeneration, smoke tests, and rollback considerations).
We are not looking to redesign the system—only to upgrade cleanly and stay consistent with ABP’s recommended practices for this template. Happy to provide access to the repo, solution overview, and any specific modules you want to inspect.
Thank you in advance for your support.
