Preliminary tasks

Before you can start your build, you must make sure that the project is ready to be built.

1. Create the new version in Addons Marketplace and update native module compatibility

2. Make sure the version number has been updated in the Core

Check the following files and update them if necessary:

• /install-dev/install_version.php:

  // update the version number below
  define('_PS_INSTALL_VERSION_', '1.7.6.2');
  

• /app/AppKernel.php:

  // Update the version number and version components (const *VERSION and the other one, which depends for patch or minor)
  const VERSION = '1.7.6.2';
  const MAJOR_VERSION_STRING = '1.7';
  const MAJOR_VERSION = 17;
  const MINOR_VERSION = 6;
  const RELEASE_VERSION = 2;
  

Make a pull request and have it merged.

Be careful: changing the version number has impacts on UI tests. You need to update the Distribution API to acknowledge the new version even though it does not exist yet, to allow UI tests to run. Submit a PR similar to this example to do so.

3. Make sure the default translation catalogue has been updated and pushed to Crowdin

1. Use the command to extract wordings from the TranslationTool repository. This command will automatically generates a Pull Request on the PrestaShop/PrestaShop repository (author should be jarvis). It is important to note that this PR must be reviewed by a member of the content team. https://github.com/PrestaShopCorp/TranslationTool is PRIVATE, and then you need a special right access to use it.

2. If the team content member requests wording corrections, they can be found either in the Prestashop CORE, a module or in the directory /mails of the Prestashop CORE.

3. If the correction occurs in a module, a release must be made, along with a bump in the composer.json of the CORE, before re-extracting.

4. If the wording to be corrected is found in /mails/themes/modern, you should first correct it in https://github.com/PrestaShop/mjml-theme-converter and the mail templates in the Prestashop CORE should also be regenerated (using https://github.com/PrestaShop/mjml-theme-converter ).

5. Once all the wordings have been corrected, validated and merged, a Github Action can be used on the TranslationTool repository to push the catalogs to Crowdin (the repository need right access).

4. Lock the theme version.

The theme has been moved outside of the Core repository since version 8.0.0.

• Create git tag on the Theme repository

When a new release is built, this tag is needed to lock the theme version.

• Tag the new version:

  git tag 2.0.0-rc1 # replace with your version
  

• Push the tag:

  git push 2.0.0-rc1 # replace with your version
  

• Update composer.lock to target the new tag

5. Manual verifications

Make sure that in the current branch:

• All license headers are correct:

  php bin/console prestashop:licenses:update
  

• All controllers are secured by annotations, and legacy link are provided for Symfony routes:

  php bin/console prestashop:linter:security-annotation
  php bin/console prestashop:linter:legacy-link
  

• There are no known vulnerabilities in composer dependencies using Fabpot Local PHP Security Checker. Consider using this if installing Fabpot Security Checker proves troublesome.

• (Minor and major releases only) – No important @todo annotations have been left forgotten in new code

• All new hooks have been registered

• The generated FOS JSON routing file is up-to-date:

  php bin/console fos:js-routing:dump \
      --format=json \
      --target=admin-dev/themes/new-theme/js/fos_js_routes.json
  

• Any new native modules have been added into composer.json and their latest versions have been updated in composer.lock:

  composer outdated -D "prestashop/*"
  

• Nightly builds are green