How to release a new PrestaShop version

This section describes the release process, step by step. A PrestaShop version release requires all these steps to be completed.


To perform a build, you will need the following:

Some of steps will require special tools or access rights which are currently not accessible for maintainers outside the PrestaShop Company. A notice indicates when this is the case.

Process overview

  1. Perform preliminary tasks:

    • Set up the new version on the PrestaShop Addons Marketplace and update native modules' compatibility.
      To allow the PrestaShop Addons Marketplace and its API to serve modules compatible with this new PrestaShop version.

    • Update the version number in the Core.

    • Make sure the default translation catalogue has been updated and pushed to Crowdin.
      To make any new wordings translatable.

    • Perform manual verifications.
      To make sure that the project is ready to be built.

  2. Create a new build:

    • Merge security PRs locally.
      Any security PRs must be merged on a local branch before making them public.

    • Update the Changelog and Contributors list.
      These files must be included in the build.

    • Build the zip archive.
      The ZIP archive contains the software (including third party dependencies) and compiled assets (Javascript and CSS), but not the development sources, dev dependencies & tests.

  3. Release the version publicly:

    • Merge security PRs on GitHub.
      And publish the security advisories.

    • Merge the updated Changelog and Contributors list on GitHub.

    • Tag the version using Git and publish the release on GitHub.

    • Release the archive on

    • Communicate.

  4. Final steps:

    • Update API stream for 1-click upgrade.
      So that the 1-Click Upgrade (autoupgrade) module becomes aware of the new release.

    • Create Docker images for the new version.

    • Go through the checklist.
      To make sure everything went all right.

Next: Preliminary tasks ›