aboutsummaryrefslogtreecommitdiff
path: root/wiki/Configuration:-Overview.md
diff options
context:
space:
mode:
authorIvan Molodetskikh <yalterz@gmail.com>2024-03-26 19:40:23 +0400
committerIvan Molodetskikh <yalterz@gmail.com>2024-03-26 19:40:23 +0400
commitcd555bbad7bbfc053e41f662ae9593b2cc88cec0 (patch)
treed2d79d0987958c5398f8b1a126613431926cbc8d /wiki/Configuration:-Overview.md
parent287d9b6b3f533c18046205cd4723a47f801962dc (diff)
downloadniri-cd555bbad7bbfc053e41f662ae9593b2cc88cec0.tar.gz
niri-cd555bbad7bbfc053e41f662ae9593b2cc88cec0.tar.bz2
niri-cd555bbad7bbfc053e41f662ae9593b2cc88cec0.zip
wiki: Clarify config breaking change between releases
Diffstat (limited to 'wiki/Configuration:-Overview.md')
-rw-r--r--wiki/Configuration:-Overview.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/wiki/Configuration:-Overview.md b/wiki/Configuration:-Overview.md
index 829b5799..6fc456d6 100644
--- a/wiki/Configuration:-Overview.md
+++ b/wiki/Configuration:-Overview.md
@@ -122,4 +122,8 @@ For example, niri used to accept multiple binds to the same key, but this was no
A patch release changed niri from silently accepting this to causing a parsing failure.
This is not a blanket rule, I will consider the potential impact of every breaking change like this before deciding to carry on with it.
+Keep in mind that the breaking change policy applies only to niri releases.
+Commits between releases can and do occasionally break the config as new features are ironed out.
+However, I do try to limit these, since several people are running git builds.
+
[KDL]: https://kdl.dev/