How to apply a patch - Enterprise Edition - Flexibility Cloud offer¶

In the following example, Akeneo PIM version 6.0.2 has just been released and we are using an Akeneo PIM version 6.0.1.

We always tag both Community and Enterprise versions with aligned version numbers, be sure to use the exact same version for CE and EE, for instance, a EE 6.0.2 fix may depend on CE 6.0.2.

Using the exact patch version will avoid any local composer cache issue.

In your enterprise standard project, the composer.json will reference both community and enterprise bundles repositories.

To upgrade, please change the composer.json to:

{
    ...
    "akeneo/pim-enterprise-dev": "6.0.2",
    ...
}

Run the composer update command:

composer --prefer-dist update

Be aware that your composer.json won’t be updated and some dependencies might be missing or from an outdated version.

You have to check whether the latest composer.json is different from your own. In this case you should backup your current composer.json and download the newest one beforehand.

Double check in the output of this command that the 6.0.2 version has been fetched, you can also check it by using the following command:

composer licenses

Then clean the cache, re-install assets and warmup the cache:

rm yarn.lock
bin/console --env=prod pim:installer:assets
yarn install
yarn run less
yarn run webpack
partners_clear_cache

If the patch is a javascript fix, please clear your browser cache before testing.

If you have an error during the yarn run webpack command, please execute this process to upgrade your package.json, reinstall the correct version of yarn modules and clean your cache.

cp vendor/akeneo/pim-enterprise-dev/std-build/package.json package.json
cp vendor/akeneo/pim-enterprise-dev/yarn.lock yarn.lock
rm -rf node_modules
yarn install
partners_php8.0-fpm restart
rm -rf var/cache/* ./public/bundles/* ./public/css/* ./public/js/*
bin/console pim:installer:assets
bin/console cache:warmup
yarn run less
make javascript-prod
make javascript-extensions