Post #37

To those who have deployed their own bot: Kindly remind that if you've enabled any service that may cause docker containers to be auto-updated to the newest image, DISABLE that. I am about to release v2.0.0 in a few days and this version will introduce some breaking changes. Manual migration is needed. From now on, you should back up your subscriptions by /export them and wait for the new version. At the same time, avoid your docker container being auto-updated. For those who are using multiuser branch, since the branch will be merged back in the future and deleted, please switch to master (for docker, it is latest) or dev branch after v2.0.0 is released. For those who are using Railway to deploy their own bot, nothing will be auto-updated unless a merge from upstream is performed. A migration guide will be provided once v2.0.0 is released. 如果你部署了自己的机器人： 温馨提示：请停用所有可能导致 docker 容器自动更新的服务。我已准备在几天内发布 v2.0.0 版本，该版本引入了一些重大变更，因而需要手动迁移。 从现在起，您应该通过 /export 备份你的订阅并等待新版本。同时，避免容器被自动更新。 对于使用 multiuser 分支的用户来说，由于 multiuser 分支将在未来被合并回去并被删除，请在 v2.0.0 发布后切换至 master (对 docker 来说是 latest) 或 dev 分支。 对于使用 Railway 部署的用户来说，自动更新不会发生，除非执行了来自上游的合并。 v2.0.0 发布时将提供迁移指南。