The latest release of the SitecoreAI base image 1.10.13 includes the following resolved issues:
The selected value comparison for Droplist field types is now case insensitive, properly displaying the selected item in the UI.
Fixed bug where Content Editor was not displaying child items under /sitecore/content/Collection/Site/Media in the content tree.
Resolved defect where page designs list could display incorrect entries if they had been previously viewed by a user with limited access permissions.
Dictionary fallback updates triggered by deleting dictionary entries are now processed asynchronously, reducing the likelihood of long-running requests and timeouts.
Fixed issue with incrementally published items with non-default language not updating changes in paths when parent folder is moved.
Upgraded the Telerik components included in the Sitecore AI Base Image from 2020.3.1021.45 to 2026.3.812 in order to improve platform quality, maintainability, and long-term supportability.
Breaking Change: Changes to JSON serialization
SitecoreAI is introducing an improvement to PipelineArgs serialization and deserialization by changing the underlying configuration from TypeNameHandling.All to TypeNameHandling.None. This change removes embedded .NET type metadata from serialized payloads and enforces more restrictive deserialization behavior.
Most implementations are not expected to be affected. Standard scenarios that use primitive values such as strings, numbers, and booleans will continue to function as before. The primary impact area is custom code that stores complex objects in PipelineArgs.CustomData and later serializes and deserializes those values.
Action required
Customers should review any serialization round-trips involving PipelineArgs.CustomData and consider using strongly typed models or explicitly reconstructing custom objects after deserialization.
To support validation and migration, a feature flag will be provided that allows customers to enable the new behavior before it becomes the default and temporarily revert if compatibility issues are discovered. We strongly recommend testing any customizations that serialize and deserialize PipelineArgs data during the notification period to identify and address potential impacts before rollout.
We also strongly recommend that you test the new security implementation before the base image release on November 29, by creating a patch configuration file and redeploying your environment.