Release 3.14.0 commit (#717)

CHANGELOG.rst

@@ -6,6 +6,27 @@ Community MySQL and MariaDB Collection Release Notes
 
 This changelog describes changes after version 2.0.0.
 
+v3.14.0
+=======
+
+Release Summary
+---------------
+
+This is a minor release of the ``community.mysql`` collection.
+This changelog contains all changes to the modules and plugins in this collection
+that have been made after the previous release.'
+
+Minor Changes
+-------------
+
+- mysql_replication - change default value for ``primary_ssl_verify_server_cert`` from False to None. This should not affect existing playbooks (https://github.com/ansible-collections/community.mysql/pull/707).
+
+Bugfixes
+--------
+
+- mysql_info - fix a crash (ERROR 1141, There is no such grant defined for user 'PUBLIC' on host '%') when using the ``users_info`` filter with a PUBLIC role present in MariaDB 10.11+. Do note that the fix doesn't change the fact that the module won't return the privileges from the PUBLIC role in the users privileges list. It can't do that because you have to login as the particular user and use `SHOW GRANTS FOR CURRENT_USER`. We considered using an aggregation with the `SHOW GRANTS FOR PUBLIC` command. However, this approach would make copying users from one server to another transform the privileges inherited from the role as if they were direct privileges on the user.
+- mysql_replication - fixed an issue where setting ``primary_ssl_verify_server_cert`` to false had no effect (https://github.com/ansible-collections/community.mysql/issues/689).
+
 v3.13.0
 =======
 

changelogs/changelog.yaml

@@ -267,6 +267,33 @@ releases:
     - 702-user_locking.yaml
     - tests_mariadb_11_4.yml
     release_date: '2025-03-21'
+  3.14.0:
+    changes:
+      bugfixes:
+      - mysql_info - fix a crash (ERROR 1141, There is no such grant defined for user
+        'PUBLIC' on host '%') when using the ``users_info`` filter with a PUBLIC role
+        present in MariaDB 10.11+. Do note that the fix doesn't change the fact that
+        the module won't return the privileges from the PUBLIC role in the users privileges
+        list. It can't do that because you have to login as the particular user and
+        use `SHOW GRANTS FOR CURRENT_USER`. We considered using an aggregation with
+        the `SHOW GRANTS FOR PUBLIC` command. However, this approach would make copying
+        users from one server to another transform the privileges inherited from the
+        role as if they were direct privileges on the user.
+      - mysql_replication - fixed an issue where setting ``primary_ssl_verify_server_cert``
+        to false had no effect (https://github.com/ansible-collections/community.mysql/issues/689).
+      minor_changes:
+      - mysql_replication - change default value for ``primary_ssl_verify_server_cert``
+        from False to None. This should not affect existing playbooks (https://github.com/ansible-collections/community.mysql/pull/707).
+      release_summary: 'This is a minor release of the ``community.mysql`` collection.
+
+        This changelog contains all changes to the modules and plugins in this collection
+
+        that have been made after the previous release.'''
+    fragments:
+    - 707-source_ssl_verify_server_cert.yml
+    - grant_to_public.yml
+    - release_3_14_0.yml
+    release_date: '2025-05-23'
   3.2.0:
     changes:
       bugfixes:

changelogs/fragments/707-source_ssl_verify_server_cert.yml

@@ -1,6 +0,0 @@
----
-bugfixes:
-  - mysql_replication - fixed an issue where setting ``primary_ssl_verify_server_cert`` to false had no effect (https://github.com/ansible-collections/community.mysql/issues/689).
-
-minor_changes:
-  - mysql_replication - change default value for ``primary_ssl_verify_server_cert`` from False to None. This should not affect existing playbooks (https://github.com/ansible-collections/community.mysql/pull/707).

changelogs/fragments/grant_to_public.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-  - mysql_info - fix a crash (ERROR 1141, There is no such grant defined for user 'PUBLIC' on host '%') when using the ``users_info`` filter with a PUBLIC role present in MariaDB 10.11+. Do note that the fix doesn't change the fact that the module won't return the privileges from the PUBLIC role in the users privileges list. It can't do that because you have to login as the particular user and use `SHOW GRANTS FOR CURRENT_USER`. We considered using an aggregation with the `SHOW GRANTS FOR PUBLIC` command. However, this approach would make copying users from one server to another transform the privileges inherited from the role as if they were direct privileges on the user.

galaxy.yml

@@ -1,7 +1,7 @@
 ---
 namespace: community
 name: mysql
-version: 3.13.0
+version: 3.14.0
 readme: README.md
 authors:
   - Ansible community