Publish command

:warning: Updated January 13, 2020: `vtex validate` command is deprecated. Use `vtex deploy` instead.

The vtex publish command, responsible for publishing new app versions, will change its platform behavior on 01/02/2020.

:warning: This release is merely a notice about the impending change to the app publishing process, meaning that **this release is not yet live** and **will only be in effect as of January 2, 2020**.

What will change

Presently, the vtex publish command automatically publishes the new version of an app, whether it was in beta or not.

From January 2, vtex publish will become just one of the three steps needed to effectively publish an app in the VTEX IO's infrastructure.


The new process will be as follows:

  1. When running the vtex publish command in your terminal, a candidate release version will be generated. The candidate release will be nothing more than a test phase, that is, the new version in probation mode. Because of this state, Housekeeper won't automatically install it on any account. To install it, you must order Toolbelt to install the exact version.
  2. After the installation, it is recommended to manually perform A/B tests on the new version, checking and confirming its stability.
  3. Once the necessary testing is completed, the third and last step is to validate the candidate release as a version that's ready to become stable on the infrastructure (having the validated status) and to be automatically installed by Housekepper. This is achieved using the vtex validate command.

Why will this action be taken

According to the command's current behavior, you can release a new stable version and publish it as fast as possible and enable it on the platform, without any of the Toolbelt requisites.

The new publication process steps strengthen the culture of these tests in addition to their validation during the development process, bringing test discipline and greater stability to the platform's apps.

Side effects

There are not deleterious app development side effects. The consequence of this release is merely the extra steps added to the publish process from January 2, 2020, on.

What you need to do

For more on this topic and to better understand the steps related to the publish process, access our recipe on Publishing an app.

Edit this page on GitHub