Repository navigation
docs(release): back up before upgrade only when the schema changes - #35
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
问题
发布文档要求每次升级前都备份完整数据目录。从镜像仓库拉取的版本，回滚只需换回旧镜像标签，只有数据库结构版本变化时旧版本才读不了升级后的数据，其余情况单独备份没有价值。
改动
docs/releasing.md说明以DATABASE_SCHEMA_REVISION是否变化决定升级前是否备份，有变化时必须备份并在更新说明中提醒用户。验证
所改 Markdown 的 Prettier 检查与
git diff --check通过，结构版本常量位置已核对。🤖 Generated with Claude Code