Another issue I don’t understand how to solve: backwards compatibility for the content-type API.
Let’s say the deployment for my next.js app along with it’s strapi cloud backend gets successfully deployed. example[dot]com v1 → example[dot]com v2. The content-type API’s have changed, and that’s okay for the next.js app since we figured it out in the previous post, but…! It’s not been fixed for all the other devices in the omnichannel (and the omnichannel stuff is the entire selling point for headless CMS’s, btw…). They still rely on the v1 api which were in api.example[dot].com. Since api.example[dot].com serves v2 content-types, all these other non-updated devices will have their frontends broken due to non-backwards compatible content apis.
How can all the devices in the omnichannel system ensure that they are using a strapi cloud instance which provides content types that they are compatible with? Is there some sort of versioning API built into strapi cloud? Should I tag up the content-types manually and never remove a committed content-type?