From 90b67d795adb3e03592de63dcff8fde1bd401fa8 Mon Sep 17 00:00:00 2001 From: Marcus B Spencer Date: Sat, 7 Mar 2026 07:03:52 -0600 Subject: [PATCH] chore(releases): update minor version criterion For some time, the minor version criterion hasn't been up to date. For instance, v2.0.16-rc.1 contains a "configuration change so that a downgrade might be problematic", but is still a patch version. --- users/releases.rst | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/users/releases.rst b/users/releases.rst index 2f674b72..40a5d31f 100644 --- a/users/releases.rst +++ b/users/releases.rst @@ -18,9 +18,8 @@ following criteria: they cannot connect to each other or otherwise can't sync files for some reason? That's a new *major* version. (This hasn't happened yet.) -- Are there changes in the REST API so that integrations or wrappers - need changes, or did the database schema or configuration change so that a - downgrade might be problematic? That's a new *minor* version. +- Are there new features (commits with type ``feat``)? That's a new + *minor* version. - If there are no specific concerns as above, it's a new *patch* version.