Shopware 6 Symfony Kernel and Asset Build Interoperability

Deployment State Consistency

In Shopware 6, the deployment process involves a sequence of Symfony kernel cache warming and the compilation of Storefront and Administration assets. Because bin/console cache:warmup is not an atomic operation, a failure during this phase can result in a hybrid state where the var/cache directory contains a mixture of legacy and partially updated container classes.

Asset Manifest Synchronization

Concurrent with the kernel cache, the frontend build process generates versioned asset manifests. If the build fails after the Symfony container has been partially updated, there is a potential mismatch between the Twig templates expecting new asset paths and the actual manifests available in the public directory.

Given the architecture of Shopware 6.5/6.6, how does the system ensure consistency between the compiled Symfony container and the asset manifests when a deployment is interrupted? Specifically, does the kernel boot process validate the existence of the corresponding build manifest before serving the storefront?