This repository has been archived by the owner on Sep 14, 2024. It is now read-only.
chore(deps): update dependency community.mysql to v3.8.0 #51
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.7.2
->3.8.0
Release Notes
ansible-collections/community.mysql (community.mysql)
v3.8.0
Compare Source
======
Release Summary
This is the 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.
Major Changes
ansible-core 2.12
andansible-core 2.13
. While we take no active measures to prevent usage and there are no plans to introduce incompatible code to the modules, we will stop testing those versions. Both are or will soon be End of Life and if you are still using them, you should consider upgrading to thelatest Ansible / ansible-core 2.15 or later
as soon as possible (https://github.com/ansible-collections/community.mysql/pull/574).column_case_sensitive
argument's default value will be changed totrue
in community.mysql 4.0.0. If your playbook expected 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).column_case_sensitive
argument's default value will be changed totrue
in community.mysql 4.0.0. 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).Minor Changes
users_info
(https://github.com/ansible-collections/community.mysql/pull/580).column_case_sensitive
option to prevent field names from being uppercased (https://github.com/ansible-collections/community.mysql/pull/569).column_case_sensitive
option to prevent field names from being uppercased (https://github.com/ansible-collections/community.mysql/pull/569).Configuration
📅 Schedule: Branch creation - "before 2pm on Saturday" in timezone Europe/Berlin, Automerge - "every weekend" in timezone Europe/Berlin.
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.