Upgrade Information

Following steps are necessary during updating to newer versions.

Upgrade to 2026.2.6

Frontend Build Ships as a Packaged Archive

The compiled Studio frontend is no longer committed as an expanded public/studio/build/ directory. It now ships as a single archive (build-dist/build-<id>.zip) that is extracted into public/studio/build/ automatically during cache warmup.

pimcore/studio-ui-bundle ^2026.2.1 is now required, as it provides the archive extraction.

Note: Read-only filesystem deployments must run bin/console cache:warmup (or cache:clear) during the build/deploy phase while the bundle directory (usually under vendor/) is still writable. Standard Pimcore deployments already do this. When assets:install runs in copy mode, run cache:warmup before it, otherwise no frontend assets are copied. If the filesystem becomes read-only before the first warmup, the bundle fails with BuildArchiveNotWritableException because there is no build to serve.

Upgrade to 2026.1.0

• The bundle installer now implements PostInstallCommandsProviderInterface from Pimcore's InstallBundle. This means the post-install command bpt:aet:rebuild-tree -a is automatically executed during pimcore:install when using Install Profiles. Manual execution of this command after pimcore:bundle:install is still required as before.
• The messenger transport DSN is now configurable via the %pimcore.messenger.transport_dsn_prefix% container parameter instead of being hardcoded to doctrine://default. This allows the installer to wire the transport DSN from environment variables (e.g. PIMCORE_MESSENGER_TRANSPORT_DSN_PREFIX).
• Added support to PHP 8.5.
• Removed support to PHP 8.3 and Symfony v6.