diff --git a/CHANGELOG.rst b/CHANGELOG.rst index 70272af..e2808d7 100644 --- a/CHANGELOG.rst +++ b/CHANGELOG.rst @@ -6,6 +6,26 @@ Community MySQL and MariaDB Collection Release Notes This changelog describes changes after version 2.0.0. +v4.0.0 +====== + +Release Summary +--------------- + +This is a major release of the ``community.mysql`` collection. +This changelog contains all breaking changes to the modules in this collection +that have been added after the release of ``community.mysql`` 3.16.0. + +Breaking Changes / Porting Guide +-------------------------------- + +- Since version 4.0.0, the collection accepts code written in Python 3. Modules aren't tested against Python 2 and might not work in Python 2 environments. +- collection - stop testing against mysqlclient connector as its support was deprecated in this collection - use PyMySQL connector instead! It'll stop working in 5.0.0 when we remove all related code (https://github.com/ansible-collections/community.mysql/issues/654). +- mysql_db - the ``pipefail`` argument's default value is set to ``true``. If your target machines do not use ``bash`` as a default interpreter, set ``pipefail`` to ``false`` explicitly. However, we strongly recommend setting up ``bash`` as a default and ``pipefail=true`` as it will protect you from getting broken dumps you don't know about (https://github.com/ansible-collections/community.mysql/issues/407). +- mysql_info - The ``users_info`` filter does not return the ``plugin_auth_string`` field anymore. Use the `plugin_hash_string` return value instead (https://github.com/ansible-collections/community.mysql/pull/629). +- mysql_role - the ``column_case_sensitive`` argument's default value has been changed to ``true``. If your playbook expected 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/578). +- mysql_user - the ``column_case_sensitive`` argument's default value has been changed to ``true``. If your playbook expected 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). + v3.16.0 ======= diff --git a/changelogs/changelog.yaml b/changelogs/changelog.yaml index ef5ec53..be59388 100644 --- a/changelogs/changelog.yaml +++ b/changelogs/changelog.yaml @@ -638,3 +638,40 @@ releases: - 602-show-all-slaves-status.yaml - 604-user-attributes.yaml release_date: '2024-02-22' + 4.0.0: + changes: + breaking_changes: + - Since version 4.0.0, the collection accepts code written in Python 3. Modules + aren't tested against Python 2 and might not work in Python 2 environments. + - collection - stop testing against mysqlclient connector as its support was + deprecated in this collection - use PyMySQL connector instead! It'll stop + working in 5.0.0 when we remove all related code (https://github.com/ansible-collections/community.mysql/issues/654). + - mysql_db - the ``pipefail`` argument's default value is set to ``true``. If + your target machines do not use ``bash`` as a default interpreter, set ``pipefail`` + to ``false`` explicitly. However, we strongly recommend setting up ``bash`` + as a default and ``pipefail=true`` as it will protect you from getting broken + dumps you don't know about (https://github.com/ansible-collections/community.mysql/issues/407). + - mysql_info - The ``users_info`` filter does not return the ``plugin_auth_string`` + field anymore. Use the `plugin_hash_string` return value instead (https://github.com/ansible-collections/community.mysql/pull/629). + - mysql_role - the ``column_case_sensitive`` argument's default value has been + changed to ``true``. If your playbook expected 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/578). + - mysql_user - the ``column_case_sensitive`` argument's default value has been + changed to ``true``. If your playbook expected 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). + release_summary: 'This is a major release of the ``community.mysql`` collection. + + This changelog contains all breaking changes to the modules in this collection + + that have been added after the release of ``community.mysql`` 3.16.0.' + fragments: + - 0-pipefail.yml + - 1-python2.yml + - 2-drop_mysql_client.yml + - 4-column_case_sensitive.yml + - 4.0.0.yml + - 5-case_sensitive2.yml + - 6-mysql_info.yml + release_date: '2025-09-16' diff --git a/changelogs/fragments/0-pipefail.yml b/changelogs/fragments/0-pipefail.yml deleted file mode 100644 index 473bd8f..0000000 --- a/changelogs/fragments/0-pipefail.yml +++ /dev/null @@ -1,2 +0,0 @@ -breaking_changes: -- mysql_db - the ``pipefail`` argument's default value is set to ``true``. If your target machines do not use ``bash`` as a default interpreter, set ``pipefail`` to ``false`` explicitly. However, we strongly recommend setting up ``bash`` as a default and ``pipefail=true`` as it will protect you from getting broken dumps you don't know about (https://github.com/ansible-collections/community.mysql/issues/407). diff --git a/changelogs/fragments/1-python2.yml b/changelogs/fragments/1-python2.yml deleted file mode 100644 index c59393a..0000000 --- a/changelogs/fragments/1-python2.yml +++ /dev/null @@ -1,2 +0,0 @@ -breaking_changes: -- Since version 4.0.0, the collection accepts code written in Python 3. Modules aren't tested against Python 2 and might not work in Python 2 environments. diff --git a/changelogs/fragments/2-drop_mysql_client.yml b/changelogs/fragments/2-drop_mysql_client.yml deleted file mode 100644 index f854395..0000000 --- a/changelogs/fragments/2-drop_mysql_client.yml +++ /dev/null @@ -1,2 +0,0 @@ -breaking_changes: -- collection - stop testing against mysqlclient connector as its support was deprecated in this collection - use PyMySQL connector instead! It'll stop working in 5.0.0 when we remove all related code (https://github.com/ansible-collections/community.mysql/issues/654). diff --git a/changelogs/fragments/4-column_case_sensitive.yml b/changelogs/fragments/4-column_case_sensitive.yml deleted file mode 100644 index ea75788..0000000 --- a/changelogs/fragments/4-column_case_sensitive.yml +++ /dev/null @@ -1,2 +0,0 @@ -breaking_changes: -- mysql_user - the ``column_case_sensitive`` argument's default value has been changed to ``true``. If your playbook expected 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). diff --git a/changelogs/fragments/5-case_sensitive2.yml b/changelogs/fragments/5-case_sensitive2.yml deleted file mode 100644 index ef46810..0000000 --- a/changelogs/fragments/5-case_sensitive2.yml +++ /dev/null @@ -1,2 +0,0 @@ -breaking_changes: -- mysql_role - the ``column_case_sensitive`` argument's default value has been changed to ``true``. If your playbook expected 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/578). diff --git a/changelogs/fragments/6-mysql_info.yml b/changelogs/fragments/6-mysql_info.yml deleted file mode 100644 index a40d4d6..0000000 --- a/changelogs/fragments/6-mysql_info.yml +++ /dev/null @@ -1,2 +0,0 @@ -breaking_changes: - - mysql_info - The ``users_info`` filter does not return the ``plugin_auth_string`` field anymore. Use the `plugin_hash_string` return value instead (https://github.com/ansible-collections/community.mysql/pull/629). diff --git a/galaxy.yml b/galaxy.yml index 6a24407..2774363 100644 --- a/galaxy.yml +++ b/galaxy.yml @@ -1,7 +1,7 @@ --- namespace: community name: mysql -version: 3.16.0 +version: 4.0.0 readme: README.md authors: - Ansible community