docs/en/release-info/migration-guides/abp-10-6.md
//[doc-seo]
{
"Description": "Upgrade your ABP solutions from v10.5 to v10.6 with this migration guide covering important behavior and integration changes."
}
This document is a guide for upgrading ABP v10.5 solutions to ABP v10.6. There are some important changes that may require action in specific application scenarios.
Package Version Changes: Before upgrading, review the Package Version Changes document to see version changes on dependent NuGet and NPM packages and align your project with ABP's internal package versions.
This version contains the following changes on the open-source side:
Who is affected
IBackgroundJobStore implementation.What changed
StoreSuccessfulJobs)AddDedicatedWorker(...))MaxParallelJobExecutionCount)IBackgroundJobStore, IBackgroundJobWorker, and related infrastructure gained new members.CompletionTime column to background job records for retention scenarios.What to do
No action is required if you do not enable the new options and do not maintain a custom background job store.
If you maintain a custom IBackgroundJobStore, implement the new interface members so your solution compiles.
If you enable StoreSuccessfulJobs, add/review the EF Core migration for the CompletionTime column and configure retention options explicitly:
Configure<AbpBackgroundJobWorkerOptions>(options =>
{
options.StoreSuccessfulJobs = true;
options.SuccessfulJobRetentionTime = TimeSpan.FromDays(7);
});
If you enable dedicated workers or parallel execution, configure the options consistently across all application instances and use a real distributed lock provider in clustered deployments.
See the Background Jobs document and #25742 for details.
Who is affected
What changed
ContentTypes and IsRemoteStream.IRemoteStreamContent as multipart FormData.FormData.RestService now unwraps ABP error envelopes more consistently for text and blob response modes.What to do
FormBodyBindingIgnoredTypes as before.FormData.See #25639 for details.
Who is affected
What changed
What to do
Who is affected
What changed
AbpAntiForgeryOptions.NormalizeUserIdClaimIssuer.What to do
Configure<AbpAntiForgeryOptions>(options =>
{
options.NormalizeUserIdClaimIssuer = false;
});
client_id FixWho is affected
What changed
client_id from the interactive authentication cookie when the cookie principal is refreshed.What to do
No action is required. Re-test authorization, account, and audit-log scenarios if you previously observed intermittent incorrect ClientId values in cookie-authenticated requests.
See #25711 for details.
Who is affected
HttpContextAbpAccessTokenProvider.client_credentials and then call other protected APIs from the same request pipeline.What changed
client_credentials requests no longer fall back to configured identity clients in that scenario.What to do
See #25740 for details.
Who is affected
ICurrentPrincipalAccessor.Principal.null principals in non-web contexts.What changed
ThreadCurrentPrincipalAccessor now returns an anonymous ClaimsPrincipal instead of null when Thread.CurrentPrincipal is not set.What to do
Principal == null.null principal.See #25752 for details.
Who is affected
Microsoft.Data.SqlClient, Swashbuckle, or Angular with fixed versions.What changed
Microsoft.* and System.* packages were upgraded to 10.0.9.Microsoft.Data.SqlClient was upgraded to 7.0.2.Swashbuckle.AspNetCore was upgraded to 10.2.3.What to do
Microsoft.Data.SqlClient.There are no explicitly marked breaking changes on the PRO side in this release scope. However, check the following if they apply to your application.
Who is affected
What changed
client_credentials requests to /connect/token.What to do
Who is affected
What changed
What to do