mirror of
https://github.com/openclaw/openclaw.git
synced 2026-06-06 05:51:15 +08:00
docs: clarify config migration policy
This commit is contained in:
@@ -38,6 +38,15 @@ Contribution rules:
|
||||
- Do not open large batches of tiny PRs at once; each PR has review cost.
|
||||
- For very small related fixes, grouping into one focused PR is encouraged.
|
||||
|
||||
Configuration compatibility:
|
||||
|
||||
OpenClaw runtime code reads the current configuration schema only.
|
||||
We do not keep long-lived aliases or compatibility branches that silently accept old, renamed, or malformed config keys.
|
||||
|
||||
When a config change makes existing user config invalid, the same change needs a doctor migration.
|
||||
`openclaw doctor --fix` should detect the old shape, explain it, back it up when needed, and rewrite it to the canonical format.
|
||||
Core-owned config and auth state are repaired in core doctor code; plugin-owned config is repaired by that plugin's doctor contract.
|
||||
|
||||
## Security
|
||||
|
||||
Security in OpenClaw is a deliberate tradeoff: strong defaults without killing capability.
|
||||
|
||||
Reference in New Issue
Block a user