Release notes for Cloud Manager 2026.8.0 in Adobe Experience Manager as a Cloud Service release-notes

Git submodule authentication for external repositories
If your external Git repository (Bring Your Own Git) uses Git submodules, Cloud Manager now automatically authenticates submodule fetches from other repositories in the same organization during pipeline builds. Previously, submodule repositories not individually registered in Cloud Manager failed authentication, so those fetches failed. Credentials are handled server-side and are never exposed to the build environment. No configuration is required, and existing pipelines continue to run without changes. (CMGR-76737)

For more information, see Git Submodule Support for Adobe Repositories.

Content sync API returns an Execution-Id for tracking
Content sync actions triggered through the Cloud Manager API now return an Execution-Id header in the response. Customers can use this identifier to track and correlate the status of a specific content sync operation, making it easier to monitor sync activity from external tooling. (CMGR-78234)

GitLab External Git (BYOG) required a manual Sync Code step for new branches
Customers using GitLab with External Git (BYOG) manually triggered a Sync Code action in Cloud Manager before the Edge Delivery Services webhook picked up a new branch. New branches are now synced automatically, removing the need for this manual step. (CMGR-77786)

Edge Delivery Services with AEM Authoring
You can now deliver sites using Edge Delivery Services while continuing to author content in AEM Author mode. Depending on your workflow preferences, you can choose from the following authoring approaches:

• Document-based authoring
• AEM-based authoring

Forms add-on incorrectly blocked on programs with Enhanced Security enabled. Customers with Enhanced Security enabled on their program were unable to add the Forms add-on to a Sites environment, even though the two are fully compatible. This restriction has been removed, and Forms can now be added normally regardless of Enhanced Security configuration. (CMGR-78266)

Content Hub credit not released after restoring an environment from soft delete. When an environment was restored from a soft-deleted state, its associated Content Hub credit remained marked as consumed even though the environment was active again. Cloud Manager now correctly re-consumes the credit on restore, ensuring credit usage accurately reflects the environment’s real state. (CMGR-78204)

Custom domain mappings stuck in Pending for EDS sites with many domains. EDS sites configured with a large number of domains experienced domain mappings that remained stuck in a Pending state indefinitely, due to a memory issue in the underlying status update process. This issue has been resolved, and domain mapping status now updates reliably regardless of domain count. (CMGR-78179)

Production-only pipelines incorrectly showed an editable Build variable service. Pipelines configured to run production deployments only, with no build phase — were still displaying “Build” as an editable environment variable service in the UI, even though no build step executed. This configuration has been corrected so the variable service list now accurately reflects the pipeline’s actual configuration. (CMGR-78120)

Pipeline execution status not updating in the UI. In certain cases, the Cloud Manager UI did not reflect the current status of a running pipeline execution, showing outdated information to the user. Pipeline execution status now updates correctly and consistently in the UI. (CMGR-77642)

EDS Sites showed a generic error when adding a collaborator failed. When adding a collaborator to an EDS site failed, the Cloud Manager UI displayed a generic error message instead of the specific failure reason. The UI now surfaces the actual error detail, helping users self-diagnose collaborator issues. (CMGR-75810)