Stay informed about important feature releases, announcements and more.
This release introduces the usage of a new configuration file format and marks the deprecation of the
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.
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
*.sphere.io (Google Cloud, Belgium),
*.commercetools.com (Google Cloud, Belgium), and
*.commercetools.co (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.