Release Notes

Stay informed about important feature releases, announcements and more.

Rewrite of Starter template

6 August 2021

The Custom Application Starter template has been rewritten from scratch, to provide a better experience to new developers working on Custom Applications.

Below an overview of the most important changes:


Custom Applications v19

8 April 2021
Breaking ChangesDependencies

The Application Kit packages have been released with a new major version v19.

This version does not contain explicit changes in our packages but mainly updates to major versions of some of the depended upon libraries. For instance:

  • @commercetools-frontend/ui-kit and all @commercetools-uikit/* packages have been updated to v12.
  • react and react-dom have been updated to v17.
  • graphql has been updated to v15.
  • webpack has been updated to v5

Furthermore, some peer dependencies have been updated to only require more recent versions. Please refer to each specific package's


GitHub Discussions available for application-kit and ui-kit repositories.

22 January 2021

GitHub Discussions is finally generally available! 🎉

We have enabled it in a few selected Open Source repositories application-kit and ui-kit.

We strongly encourage and recommend to use that as a way of communicating with us (commercetools) and with the community. You can ask questions, share ideas, showcase your work, etc.

You can still use GitHub Issues in case you have to fill an bug report.

We are really excited about it and we hope you find it useful too.

Custom Applications v18

22 January 2021
Breaking ChangesDependencies

The Application Kit packages have been released as a new major version v18.

The changes relate to @commercetools-frontend/eslint-config-mc-app package, where eslint is now the only required peer dependency. Additionally, the ESLint config uses the ESLint React App config as a base instead of Airbnb.

Most of the rules have stayed the same, however you may need to adjust or fix some depending on your usage.

In this release we also removed the long deprecated hostnames and from the default Content Security Policy configuration. This is aligned with the long-running effort of moving the Merchant Center to use the new URLs.

If you still want to support your Custom Application to run on the legacy hostname for the remaining time being, you would need to explicitly add the legacy hostname(s) in the connect-src config of the custom-application-config.json.

Follow the steps below to migrate your ESLint config to the new version.


Custom Applications v17

14 October 2020
Breaking ChangesDependencies

The Application Kit packages have been released as a new major version v17. One of the most important changes in this release is about migrating to the new Apollo Client v3.

Follow the steps below to migrate your Custom Application to the new versions.


Introducing a new and simpler application config

16 July 2020

This release introduces the usage of a new configuration file format and marks the deprecation of the env.json and headers.json files.

The env.json and headers.json files will still keep working but they will be removed in the next major release.

The new configuration format aims to drastically simplify the configuration of a Custom Application. In addition, it also strives to make the configuration process less error prone. To achieve this, the new configuration file is backed by a JSON schema that is shipped together with the new package. The configuration file is then validated against the JSON schema.

Furthermore, the new configuration process tries to infer as much information as possible to reduce the amount of required fields.


Migrate Custom Applications to the new host naming scheme

10 June 2020
Merchant CenterConfiguration

Recently we introduced a new host naming scheme for the commercetools APIs, including the Merchant Center, to increase region and cloud provider transparency.

While the previous hostnames such as * (Google Cloud, Belgium), * (Google Cloud, Belgium), and * (Google Cloud, Iowa) continue to be operational, we strongly recommend to migrate to the new hostname structure.

~~In regards to Custom Applications, the runtime configuration needs to be updated to support both the new and the legacy hostnames to allow users to log in with the new Merchant Center hostname, and to be backwards compatible with the legacy hostnames.~~

If you are using the [new application config file][/development/application-config], you can ignore the migration steps as the hostnames are automatically configured.

Here are the steps to take.

Filter by Date
Filter By Topics
Sign upLog inTech BlogIntegrationsStatusSupportUser Research Program
Copyright © 2021 commercetools
Privacy PolicyImprint