Ansible 6.0.0 #37758
Merged
Ansible 6.0.0 #37758
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jcgruenhage
force-pushed
the
ansible-6.0.0_1
branch
5 times, most recently
from
eed80c0
to
819f7cf
Compare
jcgruenhage
force-pushed
the
ansible-6.0.0_1
branch
from
819f7cf
to
aef6a71
Compare
jcgruenhage
force-pushed
the
ansible-6.0.0_1
branch
from
aef6a71
to
d28db86
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Testing the changes
First patch has been merged upstream and will become available in 2.14, second patch has been merged upstream and a backport attempt was started as well, so it might arrive in 2.13.2 already.
We finally have tests running on ansible-core again, which surfaced ansible/ansible#78169, which was fixed in under half a day by upstream, so yay :)