Keep docs in sync#10
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4362c1a3e6
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ./central-update v1.3.0-rc.1 | ||
| ``` | ||
|
|
||
| Major version jumps require explicit approval: |
There was a problem hiding this comment.
Don't promise major-upgrade approval from stable
For a fresh deploy bundle, .env.prod.example sets CENTRAL_VERSION=stable, and central-update only marks major_jump when both the current and target versions parse as vX.Y.Z; stable yields an empty current major. In that default production setup, ./central-update v2.0.0 proceeds without --allow-major and without the major-jump backup path, so this guide gives operators a safety guarantee the script does not enforce.
Useful? React with 👍 / 👎.
No description provided.