The latest release of the SitecoreAI base image 1.8.24 includes the following improvements:
Optimization of new version creation in translation jobs
The creation of new item versions during the translation process has been optimized to reduce load spikes for the SQL database and improve the accuracy of the progress indicator.
Improve translation job behavior when SitecoreAI restarts.
When a translation job is interrupted by a SitecoreAI restart, it now appears as failed rather than incorrectly appearing to be still running.
Save all blob data with fields containing base64 strings to blob storage
Move embedded media blob data to Azure Blob Storage on startup. This will improve performance as reading media content from the database is less efficient that reading it from blob storage. The migration runs once as a background job and skips resource items.
Security enhancements
The latest release of the SitecoreAI base image 1.8.24 includes the following resolved issues:
Fixed an issue where checkbox state in the Content Editor would become unchecked due to a race condition occurring during save event validation.
Resolved defect where media items stored in items-as-resources (IAR) package were not being uploaded to blob storage by adding check to verify if IARs contain blob field IDs.
Improved page stability to prevent rendering issues when processing internal and external links on pages.
Resolved issue where the Insert Link dialog in the Content Editor failed to open when there was a large number of linkable sites in the environment.
Fixed defect where the clone rendering script in the Content Editor was not creating the necessary scaffolding actions and failing to create the rendering variants folder.
Resolved an issue where supported languages did not work correctly for users without edit permissions, ensuring a consistent multilingual experience for all users.
Added additional validation logic to alt field validator on DAM connector to match kernel logic. This ensures that the DAM connector correctly validates the alt field for images when enabled.
Resolved issue where Out Of Memory exception was thrown during index rebuild when per-site standard values and language fallback are enabled.
Breaking Change: Legacy package management replaced by modern deployment and content transfer tools.
Effective July 7, 2026, the Package Designer will be transitioned to modern, supported deployment and content transfer approaches.
From this date onward, content movement, module installation, and custom code deployment will be handled through the enhanced methods outlined below, designed to provide greater reliability and alignment with cloud-native best practices.
Rollout Schedule
This change will be rolled out in stages, beginning with non-production environments.
July 7, 2026: Non-production rollout. The change is deployed to non-production environments.
July 7 to 15, 2026: Optional promotion to production.
Once validated, the change can be deployed to the production environment at any time during this window using the Deploy app.July 15, 2026: Automatic production deployment. Any production environment not already deployed will be automatically updated to this change on this date.
For full details on Sitecore SaaS update processes, please refer to: Sitecore SaaS Environment Updates Policy.
Recommended Actions
To ensure continuity of your content operations, please adopt the following supported methods:
Installing modules or custom code: Deploy these through your standard CI/CD pipeline in place of the package installer. See the DevOps | Accelerate Cookbook for SitecoreAI | Sitecore Developer Portal.
Migrating from on-premises Sitecore XM/XP: For larger, one-time migrations, use the XM to XM Cloud Migration Tool, available from the Migrate a site to SitecoreAI | Sitecore Documentation.
Moving content through a graphical interface: A dedicated content migration application will be available through the Sitecore Marketplace, providing a graphical interface for moving content between environments. See About Sitecore Marketplace.
Transferring content or media between environments: Use the Content Transfer API and the Item Transfer API to move content items and their sub-items between environments.