docs/en/Blog-Posts/2026-06-03 v10_5_Preview/POST.md
We are happy to release ABP version 10.5 RC (Release Candidate). This blog post introduces the new features and important changes in this new version.
Try this version and provide feedback for a more stable version of ABP v10.5! Thanks to you in advance.
You can check the Get Started page to see how to get started with ABP. You can either download ABP Studio (recommended, if you prefer a user-friendly GUI application - desktop application) or use the ABP CLI.
By default, ABP Studio uses stable versions to create solutions. Therefore, if you want to create a solution with a preview version, first you need to create a solution and then switch your solution to the preview version from the ABP Studio UI:
There are no explicitly marked breaking changes in this version. However, there are still some important migration notes for specific scenarios. Please check the migration guide if you are upgrading from v10.4 or earlier: ABP Version 10.5 Migration Guide.
In this section, I will introduce some major features released in this version. Here is a brief list of titles explained in the next sections:
ABP v10.5 improves the AWS Blob Storing provider so it can work with S3-compatible storage services such as Cloudflare R2, MinIO, Backblaze B2, Wasabi, and DigitalOcean Spaces.
Two new AWS blob provider configuration options are available:
ServiceURL: Sets the custom S3-compatible service endpoint.DisablePayloadSigning: Sends UNSIGNED-PAYLOAD instead of streaming chunked signing when the target provider does not support AWS SDK v4's default payload signing behavior.Example configuration:
Configure<AbpBlobStoringOptions>(options =>
{
options.Containers.ConfigureDefault(container =>
{
container.UseAws(aws =>
{
aws.AccessKeyId = "your-access-key";
aws.SecretAccessKey = "your-secret-key";
aws.ServiceURL = "https://<account-id>.r2.cloudflarestorage.com";
aws.ContainerName = "my-container";
aws.DisablePayloadSigning = true;
});
});
});
This is especially useful if you want to keep ABP's blob storing abstraction while using an S3-compatible provider instead of AWS S3 itself.
See #22962 for details.
ABP v10.5 adds opt-in default scope fallback options for OpenIddict token grants.
For client_credentials, password, and token-exchange grants, you can now configure ABP to use the scopes registered on the client application when the token request does not include a scope parameter.
The new options are disabled by default:
Configure<AbpOpenIddictAspNetCoreOptions>(options =>
{
options.UseDefaultScopesForClientCredentials = true;
options.UseDefaultScopesForPassword = true;
options.UseDefaultScopesForTokenExchange = true;
});
This gives applications more flexibility for machine-to-machine and integration scenarios while keeping the existing behavior unchanged unless you explicitly enable it.
See #25356 for details.
ABP v10.5 improves the dynamic background worker infrastructure with provider capability markers.
Consumers can now detect whether the active IDynamicBackgroundWorkerManager supports runtime registration and cron scheduling by checking marker interfaces:
ISupportsRuntimeRegistrationISupportsCronSchedulingHangfire and Quartz dynamic worker managers support both runtime registration and cron scheduling. The default in-memory manager supports runtime registration only, and now rejects cron expressions with a clearer error message. TickerQ's dynamic worker manager does not expose runtime dynamic scheduling support.
This is useful for modules and tools that need to adapt their UI or behavior based on the active background worker provider.
See #25397 for details.
ABP continues improving token security in the Account PRO module.
In v10.5, the link-user token provider now uses ABP's single-active token infrastructure. Only the latest generated link-user token remains valid, and applications can configure the token lifetime through dedicated options.
The default ASP.NET Core Identity token provider used by ABP has also been replaced with an ABP single-active variant. Password-flow challenge tokens, such as two-factor and password-change challenge flows, are now single-active per user and purpose with a short default lifetime.
These changes help reduce the risk of old tokens remaining usable after a newer token has been issued.
ABP v10.5 updates the @abp/codemirror package to CodeMirror 6.
The package keeps compatibility with existing ABP and CMS Kit integrations through a window.CodeMirror.fromTextArea(...) adapter while serving the updated bundled CodeMirror assets from the ABP package.
This modernizes the editor infrastructure used by CMS Kit and related UI features without requiring typical applications to change their CMS Kit usage.
See #25358 for details.
ABP Commercial v10.5 RC improves shared user account administration with a new tenant-side removal action.
Administrators can now remove a shared user from the current tenant directly from the user management UI. This provides an admin-managed counterpart to the self-service leave flow and keeps shared-account administration easier to handle in multi-tenant systems.
ABP v10.5 RC includes several dependency and package updates:
@abp/codemirrorCheck the Package Version Changes document for all updates.
ResourcePermissionGrant index length problem that could cause MySQL initial migration failures (#25495).MedallionAbpDistributedLock (#25497).docs/en Markdown files (#25415).As always, exciting articles have been contributed by the ABP community. I will highlight some of them here:
Thanks to the ABP Community for all the content they have published. You can also post your ABP related (text or video) content to the ABP Community.
This version comes with some new features and a lot of enhancements to the existing features. You can see the Road Map documentation to learn about the release schedule and planned features for the next releases. Please try ABP v10.5 RC and provide feedback to help us release a more stable version.
Thanks for being a part of this community!