From f47b1196045768817848e4953dfcdf75694515af Mon Sep 17 00:00:00 2001
From: Laurent Indermuehle <laurent.indermuehle@pm.me>
Date: Tue, 3 Oct 2023 15:02:57 +0200
Subject: [PATCH] add announce default will change in in 4.0.0

---
 changelogs/569_fix_column_uppercasing.yml | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/changelogs/569_fix_column_uppercasing.yml b/changelogs/569_fix_column_uppercasing.yml
index 2f2fd42..7645683 100644
--- a/changelogs/569_fix_column_uppercasing.yml
+++ b/changelogs/569_fix_column_uppercasing.yml
@@ -8,3 +8,13 @@ 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).
+  - mysql_user - the ``column_case_sensitive`` argument's default value will be
+    changed to ``true`` in community.mysql 4.0.0. If your playbook expectd the
+    column to be automatically uppercased for your users privileges, you should
+    set this to false explicitly
+    (https://github.com/ansible-collections/community.mysql/issues/577).
+  - mysql_role - the ``column_case_sensitive`` argument's default value will be
+    changed to ``true`` in community.mysql 4.0.0. If your playbook expectd the
+    column to be automatically uppercased for your roles privileges, you should
+    set this to false explicitly
+    (https://github.com/ansible-collections/community.mysql/issues/578).