1. Check out a version¶
1.1. Create a branch¶
Create a new branch for handling update changes from the project's
master branch, or from the branch you're updating on:
This creates a new project branch for the update based on your current project branch.
<branch_name> would be
In the following steps it will be referred to as update branch.
If it is not added as a remote yet, add
ezsystems/ezplatform as an
(on an Enterprise installation use
ezsystems/ezplatform-ee, and on an eZ Commerce installation,
1.3. Prepare for pulling changes¶
sort-packages option when updating from <=v1.13.4, v2.2.3, v2.3.2
Composer sorts packages listed in
If your packages are not sorted yet, you should prepare for this update to make it clearer which changes you introduce.
Assuming you have installed packages on your installation (
composer install), do the following steps:
1. Add sort-packages to the
config section in
1 2 3 4 5 6 7
composer require to get Composer to sort your packages.
The following example updates a few requirements with what you can expect in the upcoming change:
1 2 3 4
3. Check that you can install/update packages.
If Composer says there were no updates, or if it updates packages without stopping with conflicts, your preparation was successful.
4. Save your work.
1.4. Pull the tag into your branch¶
Pull the selected tag into your update branch with the following command:
Always provide the version number with the
v prefix, which indicates a tag, not a branch
v3.2.0 indicates a tag, while
3.2 indicates a development branch).
At this stage you may get conflicts, which are a normal part of the update procedure.
The most common ones will be on