Strapi transfer diverging schema's


I am trying out a workflow where we run a strapi server in develop mode to test certain layouts and content types on a development server.

Whenever we decide the content is ok, we run the strapi transfer command. This worked fine for the very first transer. But after the first one we noticed that if the source schema changes that subsequent runs of the strapi transfer just gives us warnings like “warn: (Schema Integrity) somethingsomething does not exist on destination” and it does not update the schema or content with components from the difference.

We would expect the destination to just get updated with the missing schema’s, but this is not the behaviour… What is correct way to achieve this work flow? Or are there alternatives that we are not seeing?

This topic has been created from a Discord post (1250941690127323208) to give it more visibility.
It will be on Read-Only mode here.
Join the conversation on Discord