Update dependency community.docker to v3.3.0 #27
Merged
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.1.0
->3.3.0
Release Notes
ansible-collections/community.docker
v3.3.0
Compare Source
======
Release Summary
Feature and bugfix release.
Minor Changes
archive_path
, detect whether changes are necessary based on the image ID (hash). If the existing tar archive matches the source, do nothing. Previously, each task execution re-created the archive (https://github.com/ansible-collections/community.docker/pull/500).Bugfixes
chdir
option which was ignored since community.docker 3.0.0 (https://github.com/ansible-collections/community.docker/issues/517, https://github.com/ansible-collections/community.docker/pull/518).v3.2.2
Compare Source
======
Release Summary
Bugfix release.
Bugfixes
kill_signal
option erroneously did not accept strings anymore since 3.0.0 (https://github.com/ansible-collections/community.docker/issues/505, https://github.com/ansible-collections/community.docker/pull/506).v3.2.1
Compare Source
======
Release Summary
Maintenance release with improved documentation.
v3.2.0
Compare Source
======
Release Summary
Feature and deprecation release.
Minor Changes
image_name_mismatch
option which allows to control the behavior if the container uses the image specified, but the container's configuration uses a different name for the image than the one provided to the module (https://github.com/ansible-collections/community.docker/issues/485, https://github.com/ansible-collections/community.docker/pull/488).Deprecated Features
ignore_image
option is deprecated and will be removed in community.docker 4.0.0. Useimage: ignore
incomparisons
instead (https://github.com/ansible-collections/community.docker/pull/487).purge_networks
option is deprecated and will be removed in community.docker 4.0.0. Usenetworks: strict
incomparisons
instead, and make sure to providenetworks
, with value[]
if all networks should be removed (https://github.com/ansible-collections/community.docker/pull/487).Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 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.