To specify the previous question: we cannot attach tags and version through CI/CD. The client may be one version, the backend another. What can be done in these conditions besides error monitoring via Sentry?

If it is impossible to synchronize client and backend versions through CI/CD and to tag them, and the client and server may be of different versions, besides error monitoring via Sentry, the following approaches can be applied:

• API versioning on the backend side. Support multiple API versions simultaneously so that the client can access the version that suits it.

• Feature flags. Manage the enabling/disabling of features on the client and server dynamically to minimize incompatibilities.

• Contracts and data schemas. Use schemas (e.g., JSON Schema, GraphQL) for validation and ensuring backward compatibility.

• Graceful degradation and fallback. The client should handle situations where the server does not support certain features correctly.

• Logging and tracing. In addition to Sentry, use centralized logging and request tracing to identify interaction issues between different versions.

• Documentation and communication. Clearly document versions and changes so that teams understand which versions are compatible.

These methods will help minimize problems when versions do not match and improve the stability of the application.