From ea60550c052abfa7bd335944c1163feb06f1a73c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Laurent=20Inderm=C3=BChle?= Date: Fri, 6 Oct 2023 14:55:57 +0200 Subject: [PATCH] downgrade the change severity Co-authored-by: Andrew Klychkov --- changelogs/569_fix_column_uppercasing.yml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/changelogs/569_fix_column_uppercasing.yml b/changelogs/569_fix_column_uppercasing.yml index 75c7f65..781304e 100644 --- a/changelogs/569_fix_column_uppercasing.yml +++ b/changelogs/569_fix_column_uppercasing.yml @@ -1,6 +1,5 @@ --- - -major_changes: +minor_changes: - mysql_user - add ``column_case_sensitive`` option to prevent field names from being uppercased @@ -8,6 +7,8 @@ major_changes: - mysql_role - add ``column_case_sensitive`` option to prevent field names from being uppercased (https://github.com/ansible-collections/community.mysql/pull/569). + +major_changes: - mysql_user - the ``column_case_sensitive`` argument's default value will be changed to ``true`` in community.mysql 4.0.0. If your playbook expected the column to be automatically uppercased for your users privileges, you should