diff options
| -rw-r--r-- | wiki/Configuration:-Overview.md | 7 |
1 files changed, 2 insertions, 5 deletions
diff --git a/wiki/Configuration:-Overview.md b/wiki/Configuration:-Overview.md index 8f90603f..55819593 100644 --- a/wiki/Configuration:-Overview.md +++ b/wiki/Configuration:-Overview.md @@ -135,11 +135,8 @@ A notable exception is `binds {}`: they do not get filled with defaults, so make ### Breaking Change Policy -Configuration backwards compatibility follows the Rust / Cargo semantic versioning standards. -A patch release (i.e. niri 0.1.3 to 0.1.4) must not cause a parse error on a config that worked on the previous version. - -A minor release (i.e. niri 0.1.3 to 0.2.0) *can* cause previously valid config files to stop parsing. -When niri reaches 1.0, a major release (i.e. niri 1.0 to 2.0) will be required to break config backwards compatibility. +As a rule, niri updates should not break existing config files. +(For example, the default config from niri v0.1.0 still parses fine on v25.02 as I'm writing this.) Exceptions can be made for parsing bugs. For example, niri used to accept multiple binds to the same key, but this was not intended and did not do anything (the first bind was always used). |