We are currently using CI/CD (GitHub Actions) to automatically deploy the latest version of the website to copilotj.chat. This chat interface allows users to configure the API Base to point to his server, which significantly simplifies the installation process.
However, there is one concern: if a user continues to use an older version of the server, future changes in the communication protocol between the server and the frontend could cause issues.
How can we ensure compatibility between the publicly deployed version and the servers that users are hosting themselves?
We are currently using CI/CD (GitHub Actions) to automatically deploy the latest version of the website to copilotj.chat. This chat interface allows users to configure the API Base to point to his server, which significantly simplifies the installation process.
However, there is one concern: if a user continues to use an older version of the server, future changes in the communication protocol between the server and the frontend could cause issues.
How can we ensure compatibility between the publicly deployed version and the servers that users are hosting themselves?