diff options
| author | Ivan Molodetskikh <yalterz@gmail.com> | 2024-03-26 18:47:16 +0400 |
|---|---|---|
| committer | Ivan Molodetskikh <yalterz@gmail.com> | 2024-03-26 18:47:16 +0400 |
| commit | 287d9b6b3f533c18046205cd4723a47f801962dc (patch) | |
| tree | 58da31a23c4cbac47a6bcc1ad8a709946d033908 /wiki/Configuration:-Overview.md | |
| parent | 9bd812c37af3bfe5e104c9818e317add9cd44250 (diff) | |
| download | niri-287d9b6b3f533c18046205cd4723a47f801962dc.tar.gz niri-287d9b6b3f533c18046205cd4723a47f801962dc.tar.bz2 niri-287d9b6b3f533c18046205cd4723a47f801962dc.zip | |
wiki: Clarify breaking change policy
Diffstat (limited to 'wiki/Configuration:-Overview.md')
| -rw-r--r-- | wiki/Configuration:-Overview.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/wiki/Configuration:-Overview.md b/wiki/Configuration:-Overview.md index 49456841..829b5799 100644 --- a/wiki/Configuration:-Overview.md +++ b/wiki/Configuration:-Overview.md @@ -112,9 +112,9 @@ 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) will never 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. +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. Exceptions can be made for parsing bugs. |