Skip to content

06_Upgrade.md

Latest commit

 

History

History
21 lines (12 loc) · 1.52 KB

06_Upgrade.md

File metadata and controls

21 lines (12 loc) · 1.52 KB
Raw
title Upgrade Information

Upgrade Information

The following steps are necessary when updating to newer versions.

Upgrade to 2026.4.0

  • [Listings] Search modes can contribute columns while they are applied (SearchModeAbstract.getAdditionalColumns(), default: none). They are shown via the new visibleColumns of useSelectedColumns(), can be filtered and reordered for the session, and are never stored in grid configurations or saved searches. A bundle with its own listing data query must request visibleColumns instead of selectedColumns, otherwise mode columns stay empty.

Upgrade to 2026.3.1

  • [Documents] DocumentLinkEditableValue.internalType is now typed as string | null | undefined instead of string | undefined. The link editable clears the property with null rather than undefined, so the cleared value survives JSON serialisation and actually reaches the backend. Code that assigns this property to a string | undefined variable has to widen its own type accordingly.

Upgrade to 2025.4.6

  • [Frontend build] The compiled frontend now ships as a single archive (build-dist/build-<id>.zip) instead of a committed public/build/ directory, and is extracted into public/build/ automatically during cache warmup.

Note: Read-only filesystem deployments must run bin/console cache:warmup (or cache:clear) during the build/deploy phase while vendor/ is still writable — standard Pimcore deployments already do this. When assets:install runs in copy mode, run cache:warmup before it.