From 287d9b6b3f533c18046205cd4723a47f801962dc Mon Sep 17 00:00:00 2001 From: Ivan Molodetskikh Date: Tue, 26 Mar 2024 18:47:16 +0400 Subject: wiki: Clarify breaking change policy --- wiki/Configuration:-Overview.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'wiki/Configuration:-Overview.md') 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. -- cgit