Merge remote-tracking branch 'origin/upstream-devel' into devel

.azure-pipelines/azure-pipelines.yml

@@ -31,7 +31,7 @@ variables:
   - name: fetchDepth
     value: 500
   - name: defaultContainer
-    value: quay.io/ansible/azure-pipelines-test-container:4.0.1
+    value: quay.io/ansible/azure-pipelines-test-container:6.0.0
 
 pool: Standard
 
@@ -54,14 +54,12 @@ stages:
           nameFormat: Python {0}
           testFormat: units/{0}
           targets:
-            - test: 2.7
-            - test: 3.6
-            - test: 3.7
             - test: 3.8
             - test: 3.9
             - test: '3.10'
             - test: 3.11
             - test: 3.12
+            - test: 3.13
   - stage: Windows
     dependsOn: []
     jobs:
@@ -70,45 +68,50 @@ stages:
           nameFormat: Server {0}
           testFormat: windows/{0}/1
           targets:
-            - test: 2016
+            - name: 2016 WinRM HTTP
-            - test: 2019
+              test: 2016/winrm/http
-            - test: 2022
+            - name: 2019 WinRM HTTPS
+              test: 2019/winrm/https
+            - name: 2022 WinRM HTTPS
+              test: 2022/winrm/https
+            - name: 2022 PSRP HTTP
+              test: 2022/psrp/http
+            - name: 2022 SSH Key
+              test: 2022/ssh/key
+            - name: 2025 PSRP HTTP
+              test: 2025/psrp/http
+            - name: 2025 SSH Key
+              test: 2025/ssh/key
   - stage: Remote
     dependsOn: []
     jobs:
       - template: templates/matrix.yml  # context/target
         parameters:
           targets:
-            - name: macOS 13.2
+            - name: macOS 14.3
-              test: macos/13.2
+              test: macos/14.3
-            - name: RHEL 7.9
+            - name: RHEL 9.4 py39
-              test: rhel/7.9
+              test: rhel/9.4@3.9
-            - name: RHEL 8.8 py36
+            - name: RHEL 9.4 py312
-              test: rhel/8.8@3.6
+              test: rhel/9.4@3.12
-            - name: RHEL 8.8 py311
+            - name: FreeBSD 13.4
-              test: rhel/8.8@3.11
+              test: freebsd/13.4
-            - name: RHEL 9.2 py39
+            - name: FreeBSD 14.1
-              test: rhel/9.2@3.9
+              test: freebsd/14.1
-            - name: RHEL 9.2 py311
-              test: rhel/9.2@3.11
-            - name: FreeBSD 12.4
-              test: freebsd/12.4
-            - name: FreeBSD 13.2
-              test: freebsd/13.2
           groups:
             - 1
             - 2
       - template: templates/matrix.yml  # context/controller
         parameters:
           targets:
-            - name: macOS 13.2
+            - name: macOS 14.3
-              test: macos/13.2
+              test: macos/14.3
-            - name: RHEL 8.8
+            - name: RHEL 9.4
-              test: rhel/8.8
+              test: rhel/9.4
-            - name: RHEL 9.2
+            - name: FreeBSD 13.4
-              test: rhel/9.2
+              test: freebsd/13.4
-            - name: FreeBSD 13.2
+            - name: FreeBSD 14.1
-              test: freebsd/13.2
+              test: freebsd/14.1
           groups:
             - 3
             - 4
@@ -116,52 +119,44 @@ stages:
       - template: templates/matrix.yml  # context/controller (ansible-test container management)
         parameters:
           targets:
-            - name: Alpine 3.17
+            - name: Alpine 3.20
-              test: alpine/3.17
+              test: alpine/3.20
-            - name: Alpine 3.18
+            - name: Fedora 40
-              test: alpine/3.18
+              test: fedora/40
-            - name: Fedora 38
+            - name: RHEL 9.4
-              test: fedora/38
+              test: rhel/9.4
-            - name: RHEL 8.8
+            - name: Ubuntu 24.04
-              test: rhel/8.8
+              test: ubuntu/24.04
-            - name: RHEL 9.2
-              test: rhel/9.2
-            - name: Ubuntu 22.04
-              test: ubuntu/22.04
           groups:
             - 6
   - stage: Docker
     dependsOn: []
     jobs:
-      - template: templates/matrix.yml
+      - template: templates/matrix.yml  # context/target
         parameters:
           testFormat: linux/{0}
           targets:
-            - name: Alpine 3
+            - name: Alpine 3.20
-              test: alpine3
+              test: alpine320
-            - name: CentOS 7
+            - name: Fedora 40
-              test: centos7
+              test: fedora40
-            - name: Fedora 38
-              test: fedora38
-            - name: openSUSE 15
-              test: opensuse15
-            - name: Ubuntu 20.04
-              test: ubuntu2004
             - name: Ubuntu 22.04
               test: ubuntu2204
+            - name: Ubuntu 24.04
+              test: ubuntu2404
           groups:
             - 1
             - 2
-      - template: templates/matrix.yml
+      - template: templates/matrix.yml  # context/controller
         parameters:
           testFormat: linux/{0}
           targets:
-            - name: Alpine 3
+            - name: Alpine 3.20
-              test: alpine3
+              test: alpine320
-            - name: Fedora 38
+            - name: Fedora 40
-              test: fedora38
+              test: fedora40
-            - name: Ubuntu 22.04
+            - name: Ubuntu 24.04
-              test: ubuntu2204
+              test: ubuntu2404
           groups:
             - 3
             - 4
@@ -174,9 +169,9 @@ stages:
           nameFormat: Python {0}
           testFormat: galaxy/{0}/1
           targets:
-            - test: '3.10'
             - test: 3.11
             - test: 3.12
+            - test: 3.13
   - stage: Generic
     dependsOn: []
     jobs:
@@ -185,9 +180,9 @@ stages:
           nameFormat: Python {0}
           testFormat: generic/{0}/1
           targets:
-            - test: '3.10'
             - test: 3.11
             - test: 3.12
+            - test: 3.13
   - stage: Incidental_Windows
     displayName: Incidental Windows
     dependsOn: []
@@ -197,9 +192,20 @@ stages:
           nameFormat: Server {0}
           testFormat: i/windows/{0}
           targets:
-            - test: 2016
+            - name: 2016 WinRM HTTP
-            - test: 2019
+              test: 2016/winrm/http
-            - test: 2022
+            - name: 2019 WinRM HTTPS
+              test: 2019/winrm/https
+            - name: 2022 WinRM HTTPS
+              test: 2022/winrm/https
+            - name: 2022 PSRP HTTP
+              test: 2022/psrp/http
+            - name: 2022 SSH Key
+              test: 2022/ssh/key
+            - name: 2025 PSRP HTTP
+              test: 2025/psrp/http
+            - name: 2025 SSH Key
+              test: 2025/ssh/key
   - stage: Incidental
     dependsOn: []
     jobs:
@@ -209,8 +215,6 @@ stages:
           targets:
             - name: IOS Python
               test: ios/csr1000v/
-            - name: VyOS Python
-              test: vyos/1.1.8/
   - stage: Summary
     condition: succeededOrFailed()
     dependsOn:

.azure-pipelines/commands/incidental/vyos.sh

@@ -1 +0,0 @@
-network.sh

.azure-pipelines/commands/incidental/windows.sh

@@ -6,6 +6,8 @@ declare -a args
 IFS='/:' read -ra args <<< "$1"
 
 version="${args[1]}"
+connection="${args[2]}"
+connection_setting="${args[3]}"
 
 target="shippable/windows/incidental/"
 
@@ -26,11 +28,7 @@ if [ -s /tmp/windows.txt ] || [ "${CHANGED:+$CHANGED}" == "" ]; then
     echo "Detected changes requiring integration tests specific to Windows:"
     cat /tmp/windows.txt
 
-    echo "Running Windows integration tests for multiple versions concurrently."
+    echo "Running Windows integration tests for the version ${version}."
-
-    platforms=(
-        --windows "${version}"
-    )
 else
     echo "No changes requiring integration tests specific to Windows were detected."
     echo "Running Windows integration tests for a single version only: ${single_version}"
@@ -39,14 +37,10 @@ else
         echo "Skipping this job since it is for: ${version}"
         exit 0
     fi
-
-    platforms=(
-        --windows "${version}"
-    )
 fi
 
 # shellcheck disable=SC2086
 ansible-test windows-integration --color -v --retry-on-error "${target}" ${COVERAGE:+"$COVERAGE"} ${CHANGED:+"$CHANGED"} ${UNSTABLE:+"$UNSTABLE"} \
-    "${platforms[@]}" \
+    --controller "docker:default,python=${python_default}" \
-    --docker default --python "${python_default}" \
+    --target "remote:windows/${version},connection=${connection}+${connection_setting},provider=${provider}" \
-    --remote-terminate always --remote-stage "${stage}" --remote-provider "${provider}"
+    --remote-terminate always --remote-stage "${stage}"

.azure-pipelines/commands/windows.sh

@@ -6,7 +6,9 @@ declare -a args
 IFS='/:' read -ra args <<< "$1"
 
 version="${args[1]}"
-group="${args[2]}"
+connection="${args[2]}"
+connection_setting="${args[3]}"
+group="${args[4]}"
 
 target="shippable/windows/group${group}/"
 
@@ -31,11 +33,7 @@ if [ -s /tmp/windows.txt ] || [ "${CHANGED:+$CHANGED}" == "" ]; then
     echo "Detected changes requiring integration tests specific to Windows:"
     cat /tmp/windows.txt
 
-    echo "Running Windows integration tests for multiple versions concurrently."
+    echo "Running Windows integration tests for the version ${version}."
-
-    platforms=(
-        --windows "${version}"
-    )
 else
     echo "No changes requiring integration tests specific to Windows were detected."
     echo "Running Windows integration tests for a single version only: ${single_version}"
@@ -44,17 +42,13 @@ else
         echo "Skipping this job since it is for: ${version}"
         exit 0
     fi
-
-    platforms=(
-        --windows "${version}"
-    )
 fi
 
-for version in "${python_versions[@]}"; do
+for py_version in "${python_versions[@]}"; do
     changed_all_target="all"
     changed_all_mode="default"
 
-    if [ "${version}" == "${python_default}" ]; then
+    if [ "${py_version}" == "${python_default}" ]; then
         # smoketest tests
         if [ "${CHANGED}" ]; then
             # with change detection enabled run tests for anything changed
@@ -80,7 +74,7 @@ for version in "${python_versions[@]}"; do
     fi
 
     # terminate remote instances on the final python version tested
-    if [ "${version}" = "${python_versions[-1]}" ]; then
+    if [ "${py_version}" = "${python_versions[-1]}" ]; then
         terminate="always"
     else
         terminate="never"
@@ -88,7 +82,8 @@ for version in "${python_versions[@]}"; do
 
     # shellcheck disable=SC2086
     ansible-test windows-integration --color -v --retry-on-error "${ci}" ${COVERAGE:+"$COVERAGE"} ${CHANGED:+"$CHANGED"} ${UNSTABLE:+"$UNSTABLE"} \
-        "${platforms[@]}" --changed-all-target "${changed_all_target}" --changed-all-mode "${changed_all_mode}" \
+        --changed-all-target "${changed_all_target}" --changed-all-mode "${changed_all_mode}" \
-        --docker default --python "${version}" \
+        --controller "docker:default,python=${py_version}" \
-        --remote-terminate "${terminate}" --remote-stage "${stage}" --remote-provider "${provider}"
+        --target "remote:windows/${version},connection=${connection}+${connection_setting},provider=${provider}" \
+        --remote-terminate "${terminate}" --remote-stage "${stage}"
 done

.azure-pipelines/scripts/combine-coverage.py

@@ -7,8 +7,7 @@ Keep in mind that Azure Pipelines does not enforce unique job display names (onl
 It is up to pipeline authors to avoid name collisions when deviating from the recommended format.
 """
 
-from __future__ import (absolute_import, division, print_function)
+from __future__ import annotations
-__metaclass__ = type
 
 import os
 import re

.azure-pipelines/scripts/publish-codecov.py

@@ -4,6 +4,7 @@ Upload code coverage reports to codecov.io.
 Multiple coverage files from multiple languages are accepted and aggregated after upload.
 Python coverage, as well as PowerShell and Python stubs can all be uploaded.
 """
+from __future__ import annotations
 
 import argparse
 import dataclasses

.azure-pipelines/scripts/time-command.py

@@ -1,8 +1,7 @@
 #!/usr/bin/env python
 """Prepends a relative timestamp to each input line from stdin and writes it to stdout."""
 
-from __future__ import (absolute_import, division, print_function)
+from __future__ import annotations
-__metaclass__ = type
 
 import sys
 import time

.git-blame-ignore-revs

@@ -2,3 +2,5 @@
 # Bulk PowerShell sanity fixes
 6def4a3180fe03981ba64c6d8db28fed3bb39c0c
 716631189cb5a3f66b3add98f39e64e98bc17bf7
+# Bulk update of strings from triple single quotes to triple double quotes
+a0495fc31497798a7a833ba7406a9729e1528dd8

.github/CONTRIBUTING.md

@@ -4,22 +4,75 @@ Hi! Nice to see you here!
 
 ## QUESTIONS ?
 
-Please see the [Community Guide](https://docs.ansible.com/ansible/latest/community/index.html) for information on how to ask questions on the [mailing lists](https://docs.ansible.com/ansible/latest/community/communication.html#mailing-list-information) and IRC.
+If you have questions about anything related to Ansible, get in touch with us!
+See [Communicating with the Ansible community](https://docs.ansible.com/ansible/devel/community/communication.html) to find out how.
 
-The GitHub issue tracker is not the best place for questions for various reasons, but both IRC and the mailing list are very helpful places for those things, as the community page explains best.
+The [Community Guide](https://docs.ansible.com/ansible/devel/community/index.html) also explains how to contribute
+and interact with the project, including how to submit bug reports and code to Ansible.
+
+Please note that the GitHub issue tracker is not the best place to ask questions for several reasons.
+You'll get more helpful, and quicker, responses in the forum.
 
 ## CONTRIBUTING ?
 
-By contributing you agree that these contributions are your own (or approved by your employer) and you grant a full, complete, irrevocable copyright license to all users and developers of the project, present and future, pursuant to the license of the project. You can also read the same [CLA](https://docs.ansible.com/ansible/latest/community/contributor_license_agreement.html) on the Ansible docsite.
+By contributing to this project you agree to the [Developer Certificate of Origin (DCO)](#developer-certificate-of-origin-dco).
+
+The Ansible project is licensed under the [GPL-3.0](COPYING) or later. Some portions of the code fall under other licenses as noted in individual files.
 
-Please review the [Community Guide](https://docs.ansible.com/ansible/latest/community/index.html) for more information on contributing to Ansible.
+The Ansible project accepts contributions through GitHub pull requests.
+Please review the [Community Guide](https://docs.ansible.com/ansible/devel/community/index.html) for more information on contributing to Ansible.
 
 ## BUG TO REPORT ?
 
-First and foremost, also check the [Community Guide](https://docs.ansible.com/ansible/latest/community/index.html).
+First and foremost, also check the [Community Guide](https://docs.ansible.com/ansible/devel/community/index.html).
 
-You can report bugs or make enhancement requests at the [Ansible GitHub issue page](http://github.com/ansible/ansible/issues/new/choose) by filling out the issue template that will be presented.
+You can report bugs or make enhancement requests at
+the [Ansible GitHub issue page](http://github.com/ansible/ansible/issues/new/choose) by filling out the issue template that will be presented.
 
-Also please make sure you are testing on the latest released version of Ansible or the development branch; see the [Installation Guide](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html) for details.
+Also please make sure you are testing on the latest released version of Ansible or the development branch.
+See the [Installation Guide](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html) for details.
 
 Thanks!
+
+## DEVELOPER CERTIFICATE OF ORIGIN (DCO)
+
+This document was created by the Linux Kernel community and is a simple statement that you, as a contributor, have the legal right to make the contribution.
+
+```text
+Developer Certificate of Origin
+Version 1.1
+
+Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
+1 Letterman Drive
+Suite D4700
+San Francisco, CA, 94129
+
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
+
+Developer's Certificate of Origin 1.1
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I
+    have the right to submit it under the open source license
+    indicated in the file; or
+
+(b) The contribution is based upon previous work that, to the best
+    of my knowledge, is covered under an appropriate open source
+    license and I have the right under that license to submit that
+    work with modifications, whether created in whole or in part
+    by me, under the same open source license (unless I am
+    permitted to submit under a different license), as indicated
+    in the file; or
+
+(c) The contribution was provided directly to me by some other
+    person who certified (a), (b) or (c) and I have not modified
+    it.
+
+(d) I understand and agree that this project and the contribution
+    are public and that a record of the contribution (including all
+    personal information I submit with it, including my sign-off) is
+    maintained indefinitely and may be redistributed consistent with
+    this project or the open source license(s) involved.
+```

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -19,13 +19,14 @@ body:
       Also test if the latest release and devel branch are affected too.
 
 
-      **Tip:** If you are seeking community support, please consider
+      **Tip:** If you are seeking community support, please see
-      [starting a mailing list thread or chatting in IRC][ML||IRC].
+      [Communicating with the Ansible community][communication] to
+      get in touch and ask questions.
 
 
 
-      [ML||IRC]:
+      [communication]:
-      https://docs.ansible.com/ansible-core/devel/community/communication.html?utm_medium=github&utm_source=issue_form--bug_report.yml#mailing-list-information
+      https://docs.ansible.com/ansible/devel/community/communication.html
 
       [issue search]: ../search?q=is%3Aissue&type=issues
 
@@ -54,7 +55,7 @@ body:
           <em>Why?</em>
         </summary>
 
-        We would do it by ourselves but unfortunatelly, the curent
+        We would do it by ourselves but unfortunately, the current
         edition of GitHub Issue Forms Alpha does not support this yet 🤷
 
 
@@ -87,7 +88,7 @@ body:
 
 
       [collections org]: /ansible-collections
-    placeholder: dnf, apt, yum, pip, user etc.
+    placeholder: dnf, apt, pip, user etc.
   validations:
     required: true
 
@@ -249,7 +250,7 @@ body:
 
 
       [ansibot help]:
-      /ansible/ansibullbot/blob/master/ISSUE_HELP.md#for-issue-submitters
+      /ansible/ansibotmini#ansibotmini
 
 
 - type: checkboxes
@@ -258,7 +259,7 @@ body:
     description: |
       Read the [Ansible Code of Conduct][CoC] first.
 
-      [CoC]: https://docs.ansible.com/ansible/latest/community/code_of_conduct.html?utm_medium=github&utm_source=issue_form--bug_report.yml
+      [CoC]: https://docs.ansible.com/ansible/devel/community/code_of_conduct.html?utm_medium=github&utm_source=issue_form--bug_report.yml
     options:
     - label: I agree to follow the Ansible Code of Conduct
       required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -2,7 +2,7 @@
 blank_issues_enabled: false  # default: true
 contact_links:
 - name: 🔐 Security bug report 🔥
-  url: https://docs.ansible.com/ansible/latest/community/reporting_bugs_and_features.html?utm_medium=github&utm_source=issue_template_chooser
+  url: https://docs.ansible.com/ansible/devel/community/reporting_bugs_and_features.html?utm_medium=github&utm_source=issue_template_chooser
   about: |
     Please learn how to report security vulnerabilities here.
 
@@ -11,12 +11,12 @@ contact_links:
     a prompt response.
 
     For more information, see
-    https://docs.ansible.com/ansible/latest/community/reporting_bugs_and_features.html
+    https://docs.ansible.com/ansible/devel/community/reporting_bugs_and_features.html
 - name: 📝 Ansible Code of Conduct
-  url: https://docs.ansible.com/ansible/latest/community/code_of_conduct.html?utm_medium=github&utm_source=issue_template_chooser
+  url: https://docs.ansible.com/ansible/devel/community/code_of_conduct.html?utm_medium=github&utm_source=issue_template_chooser
   about: ❤ Be nice to other members of the community. ☮ Behave.
-- name: 💬 Talks to the community
+- name: 💬 Talk to the community
-  url: https://docs.ansible.com/ansible/latest/community/communication.html?utm_medium=github&utm_source=issue_template_chooser#mailing-list-information
+  url: https://docs.ansible.com/ansible/devel/community/communication.html?utm_medium=github&utm_source=issue_template_chooser#mailing-list-information
   about: Please ask and answer usage questions here
 - name: ⚡ Working groups
   url: https://github.com/ansible/community/wiki

.github/ISSUE_TEMPLATE/documentation_report.yml

@@ -22,12 +22,14 @@ body:
       Also test if the latest release and devel branch are affected too.
 
 
-      **Tip:** If you are seeking community support, please consider
+      **Tip:** If you are seeking community support, please see
-      [starting a mailing list thread or chatting in IRC][ML||IRC].
+      [Communicating with the Ansible community][communication] to
+      get in touch and ask questions.
 
 
-      [ML||IRC]:
+
-      https://docs.ansible.com/ansible-core/devel/community/communication.html?utm_medium=github&utm_source=issue_form--documentation_report.yml#mailing-list-information
+      [communication]:
+      https://docs.ansible.com/ansible/devel/community/communication.html
 
       [issue search]: ../search?q=is%3Aissue&type=issues
 
@@ -196,7 +198,7 @@ body:
 
 
       [ansibot help]:
-      /ansible/ansibullbot/blob/master/ISSUE_HELP.md#for-issue-submitters
+      /ansible/ansibotmini#ansibotmini
 
 
 - type: checkboxes
@@ -205,7 +207,7 @@ body:
     description: |
       Read the [Ansible Code of Conduct][CoC] first.
 
-      [CoC]: https://docs.ansible.com/ansible/latest/community/code_of_conduct.html?utm_medium=github&utm_source=issue_form--documentation_report.yml
+      [CoC]: https://docs.ansible.com/ansible/devel/community/code_of_conduct.html?utm_medium=github&utm_source=issue_form--documentation_report.yml
     options:
     - label: I agree to follow the Ansible Code of Conduct
       required: true

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -21,8 +21,7 @@ body:
 
       If unsure, consider filing a [new proposal] instead outlining your
       use-cases, the research and implementation considerations. Then,
-      start a discussion on one of the public [IRC meetings] we have just
+      start a discussion in the [Ansible forum][forum].
-      for this.
 
 
       <details>
@@ -44,21 +43,22 @@ body:
       Also test if the devel branch does not already implement this.
 
 
-      **Tip:** If you are seeking community support, please consider
+      **Tip:** If you are seeking community support, please see
-      [starting a mailing list thread or chatting in IRC][ML||IRC].
+      [Communicating with the Ansible community][communication] to
+      get in touch and ask questions.
 
 
 
       [contribute to collections]:
       https://docs.ansible.com/ansible-core/devel/community/contributing_maintained_collections.html?utm_medium=github&utm_source=issue_form--feature_request.yml
 
-      [IRC meetings]:
+      [communication]:
-        https://docs.ansible.com/ansible-core/devel/community/communication.html?utm_medium=github&utm_source=issue_form--feature_request.yml#irc-meetings
+      https://docs.ansible.com/ansible/devel/community/communication.html
 
       [issue search]: ../search?q=is%3Aissue&type=issues
 
-      [ML||IRC]:
+      [forum help]:
-      https://docs.ansible.com/ansible-core/devel/community/communication.html?utm_medium=github&utm_source=issue_form--feature_request.yml#mailing-list-information
+      https://forum.ansible.com/c/help/6
 
       [new proposal]: ../../proposals/issues/new
 
@@ -109,7 +109,7 @@ body:
           <em>Why?</em>
         </summary>
 
-        We would do it by ourselves but unfortunatelly, the curent
+        We would do it by ourselves but unfortunately, the current
         edition of GitHub Issue Forms Alpha does not support this yet 🤷
 
 
@@ -139,7 +139,7 @@ body:
 
 
       [collections org]: /ansible-collections
-    placeholder: dnf, apt, yum, pip, user etc.
+    placeholder: dnf, apt, pip, user etc.
   validations:
     required: true
 
@@ -176,7 +176,7 @@ body:
 
 
       [ansibot help]:
-      /ansible/ansibullbot/blob/master/ISSUE_HELP.md#for-issue-submitters
+      /ansible/ansibotmini#ansibotmini
 
 
 - type: checkboxes
@@ -185,7 +185,7 @@ body:
     description: |
       Read the [Ansible Code of Conduct][CoC] first.
 
-      [CoC]: https://docs.ansible.com/ansible/latest/community/code_of_conduct.html?utm_medium=github&utm_source=issue_form--feature_request.yml
+      [CoC]: https://docs.ansible.com/ansible/devel/community/code_of_conduct.html?utm_medium=github&utm_source=issue_form--feature_request.yml
     options:
     - label: I agree to follow the Ansible Code of Conduct
       required: true

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,29 +0,0 @@
-##### SUMMARY
-
-<!--- Describe the change below, including rationale and design decisions -->
-
-<!--- HINT: Include "Fixes #nnn" if you are fixing an existing issue -->
-
-##### ISSUE TYPE
-
-<!--- Pick one below and delete the rest -->
-
-- Bugfix Pull Request
-- Docs Pull Request
-- Feature Pull Request
-- Test Pull Request
-
-##### COMPONENT NAME
-
-<!--- Write the short name of the module, plugin, task or feature below -->
-
-##### ADDITIONAL INFORMATION
-
-<!--- Include additional information to help people understand the change here -->
-<!--- A step-by-step reproduction of the problem is helpful if there is no related issue -->
-
-<!--- Paste verbatim command output below, e.g. before and after your change -->
-
-```paste below
-
-```

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1 @@
+PULL_REQUEST_TEMPLATE/Unclear purpose or motivation.md

.github/PULL_REQUEST_TEMPLATE/Bug fix.md

@@ -0,0 +1,20 @@
+##### SUMMARY
+
+<!--- Describe the change below, including rationale and design decisions -->
+
+<!--- HINT: Include "Fixes #nnn" if you are fixing an existing issue -->
+
+##### ISSUE TYPE
+
+- Bugfix Pull Request
+
+##### ADDITIONAL INFORMATION
+
+<!--- Include additional information to help people understand the change here -->
+<!--- A step-by-step reproduction of the problem is helpful if there is no related issue -->
+
+<!--- Paste verbatim command output below, e.g. before and after your change -->
+
+```paste below
+
+```

.github/PULL_REQUEST_TEMPLATE/Documentation change.md

@@ -0,0 +1,19 @@
+##### SUMMARY
+
+<!--- Describe the change below, including rationale -->
+
+<!--- HINT: Include "Closes #nnn" if you are fixing an existing issue -->
+
+##### ISSUE TYPE
+
+- Docs Pull Request
+
+##### ADDITIONAL INFORMATION
+
+<!--- Include additional information to help people understand the change here -->
+
+<!--- Paste verbatim command output below, e.g. before and after your change -->
+
+```paste below
+
+```

.github/PULL_REQUEST_TEMPLATE/New feature.md

@@ -0,0 +1,19 @@
+##### SUMMARY
+
+<!--- Describe the change below, including rationale and design decisions -->
+
+<!--- HINT: Include "Resolves #nnn" if you are fixing an existing issue -->
+
+##### ISSUE TYPE
+
+- Feature Pull Request
+
+##### ADDITIONAL INFORMATION
+
+<!--- Include additional information to help people understand the change here -->
+
+<!--- Paste verbatim command output below, e.g. before and after your change -->
+
+```paste below
+
+```

.github/PULL_REQUEST_TEMPLATE/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1 @@
+Unclear purpose or motivation.md

.github/PULL_REQUEST_TEMPLATE/Tests.md

@@ -0,0 +1,20 @@
+##### SUMMARY
+
+<!--- Describe the change below, including rationale and design decisions -->
+
+<!--- HINT: Include "Closes #nnn" if you are fixing an existing issue -->
+
+##### ISSUE TYPE
+
+- Test Pull Request
+
+##### ADDITIONAL INFORMATION
+
+<!--- Include additional information to help people understand the change here -->
+<!--- A step-by-step reproduction of the problem is helpful if there is no related issue -->
+
+<!--- Paste verbatim command output below, e.g. before and after your change -->
+
+```paste below
+
+```

.github/PULL_REQUEST_TEMPLATE/Unclear purpose or motivation.md

@@ -0,0 +1,25 @@
+##### SUMMARY
+
+<!--- Describe the change below, including rationale and design decisions -->
+
+<!--- HINT: Include "Fixes #nnn" if you are fixing an existing issue -->
+
+##### ISSUE TYPE
+
+<!--- Pick one below and delete the rest -->
+
+- Bugfix Pull Request
+- Docs Pull Request
+- Feature Pull Request
+- Test Pull Request
+
+##### ADDITIONAL INFORMATION
+
+<!--- Include additional information to help people understand the change here -->
+<!--- A step-by-step reproduction of the problem is helpful if there is no related issue -->
+
+<!--- Paste verbatim command output below, e.g. before and after your change -->
+
+```paste below
+
+```

.github/RELEASE_NAMES.txt

@@ -1,3 +1,6 @@
+2.19.0  What Is and What Should Never Be
+2.18.0  Fool in the Rain
+2.17.0  Gallows Pole
 2.16.0  All My Love
 2.15.0  Ten Years Gone
 2.14.0  C'mon Everybody

.gitignore

@@ -92,6 +92,8 @@ Vagrantfile
 /lib/ansible_base.egg-info/
 # First used in the `devel` branch during Ansible 2.11 development.
 /lib/ansible_core.egg-info/
+# First used in the `devel` branch during Ansible 2.18 development.
+/ansible_core.egg-info/
 # vendored lib dir
 lib/ansible/_vendor/*
 !lib/ansible/_vendor/__init__.py

MANIFEST.in

@@ -1,12 +1,10 @@
 include COPYING
-include bin/*
 include changelogs/CHANGELOG*.rst
 include changelogs/changelog.yaml
 include licenses/*.txt
 include requirements.txt
-recursive-include docs *
 recursive-include packaging *.py *.j2
 recursive-include test/integration *
-recursive-include test/sanity *.in *.json *.py *.txt
+recursive-include test/sanity *.in *.json *.py *.txt *.ini
 recursive-include test/support *.py *.ps1 *.psm1 *.cs *.md
 recursive-include test/units *

README.md

@@ -1,9 +1,9 @@
 [![PyPI version](https://img.shields.io/pypi/v/ansible-core.svg)](https://pypi.org/project/ansible-core)
 [![Docs badge](https://img.shields.io/badge/docs-latest-brightgreen.svg)](https://docs.ansible.com/ansible/latest/)
-[![Chat badge](https://img.shields.io/badge/chat-IRC-brightgreen.svg)](https://docs.ansible.com/ansible/latest/community/communication.html)
+[![Chat badge](https://img.shields.io/badge/chat-IRC-brightgreen.svg)](https://docs.ansible.com/ansible/devel/community/communication.html)
 [![Build Status](https://dev.azure.com/ansible/ansible/_apis/build/status/CI?branchName=devel)](https://dev.azure.com/ansible/ansible/_build/latest?definitionId=20&branchName=devel)
-[![Ansible Code of Conduct](https://img.shields.io/badge/code%20of%20conduct-Ansible-silver.svg)](https://docs.ansible.com/ansible/latest/community/code_of_conduct.html)
+[![Ansible Code of Conduct](https://img.shields.io/badge/code%20of%20conduct-Ansible-silver.svg)](https://docs.ansible.com/ansible/devel/community/code_of_conduct.html)
-[![Ansible mailing lists](https://img.shields.io/badge/mailing%20lists-Ansible-orange.svg)](https://docs.ansible.com/ansible/latest/community/communication.html#mailing-list-information)
+[![Ansible mailing lists](https://img.shields.io/badge/mailing%20lists-Ansible-orange.svg)](https://docs.ansible.com/ansible/devel/community/communication.html#mailing-list-information)
 [![Repository License](https://img.shields.io/badge/license-GPL%20v3.0-brightgreen.svg)](COPYING)
 [![Ansible CII Best Practices certification](https://bestpractices.coreinfrastructure.org/projects/2372/badge)](https://bestpractices.coreinfrastructure.org/projects/2372)
 
@@ -40,21 +40,33 @@ features and fixes, directly. Although it is reasonably stable, you are more lik
 breaking changes when running the `devel` branch. We recommend getting involved
 in the Ansible community if you want to run the `devel` branch.
 
-## Get Involved
+## Communication
 
-* Read [Community Information](https://docs.ansible.com/ansible/latest/community) for all
+Join the Ansible forum to ask questions, get help, and interact with the
+community.
+
+* [Get Help](https://forum.ansible.com/c/help/6): Find help or share your Ansible knowledge to help others.
+  Use tags to filter and subscribe to posts, such as the following:
+  * Posts tagged with [ansible](https://forum.ansible.com/tag/ansible)
+  * Posts tagged with [ansible-core](https://forum.ansible.com/tag/ansible-core)
+  * Posts tagged with [playbook](https://forum.ansible.com/tag/playbook)
+* [Social Spaces](https://forum.ansible.com/c/chat/4): Meet and interact with fellow enthusiasts.
+* [News & Announcements](https://forum.ansible.com/c/news/5): Track project-wide announcements including social events.
+* [Bullhorn newsletter](https://docs.ansible.com/ansible/devel/community/communication.html#the-bullhorn): Get release announcements and important changes.
+
+For more ways to get in touch, see [Communicating with the Ansible community](https://docs.ansible.com/ansible/devel/community/communication.html).
+
+## Contribute to Ansible
+
+* Check out the [Contributor's Guide](./.github/CONTRIBUTING.md).
+* Read [Community Information](https://docs.ansible.com/ansible/devel/community) for all
   kinds of ways to contribute to and interact with the project,
-  including mailing list information and how to submit bug reports and
+  including how to submit bug reports and code to Ansible.
-  code to Ansible.
-* Join a [Working Group](https://github.com/ansible/community/wiki),
-  an organized community devoted to a specific technology domain or platform.
 * Submit a proposed code update through a pull request to the `devel` branch.
 * Talk to us before making larger changes
   to avoid duplicate efforts. This not only helps everyone
   know what is going on, but it also helps save time and effort if we decide
   some changes are needed.
-* For a list of email lists, IRC channels and Working Groups, see the
-  [Communication page](https://docs.ansible.com/ansible/latest/community/communication.html)
 
 ## Coding Guidelines
 
@@ -67,7 +79,7 @@ We document our Coding Guidelines in the [Developer Guide](https://docs.ansible.
 
 * The `devel` branch corresponds to the release actively under development.
 * The `stable-2.X` branches correspond to stable releases.
-* Create a branch based on `devel` and set up a [dev environment](https://docs.ansible.com/ansible/latest/dev_guide/developing_modules_general.html#common-environment-setup) if you want to open a PR.
+* Create a branch based on `devel` and set up a [dev environment](https://docs.ansible.com/ansible/devel/dev_guide/developing_modules_general.html#common-environment-setup) if you want to open a PR.
 * See the [Ansible release and maintenance](https://docs.ansible.com/ansible/devel/reference_appendices/release_and_maintenance.html) page for information about active branches.
 
 ## Roadmap

bin/ansible-connection

@@ -1 +0,0 @@
-../lib/ansible/cli/scripts/ansible_connection_cli_stub.py

changelogs/changelog.yaml

@@ -1,2 +1,2 @@
-ancestor: 2.15.0
+ancestor: 2.18.0
 releases: {}

changelogs/fragments/22396-indicate-which-args-are-multi.yml

@@ -1,3 +0,0 @@
-minor_changes:
-- CLI argument parsing - Automatically prepend to the help of CLI arguments that support being specified multiple times.
-  (https://github.com/ansible/ansible/issues/22396)

changelogs/fragments/27816-fetch-unreachable.yml

@@ -1,2 +0,0 @@
-bugfixes:
-- fetch - Handle unreachable errors properly (https://github.com/ansible/ansible/issues/27816)

changelogs/fragments/50603-tty-check.yaml

@@ -1,4 +0,0 @@
----
-minor_changes:
-  - "ansible-vault create: Now raises an error when opening the editor without
-    tty. The flag --skip-tty-check restores previous behaviour."

changelogs/fragments/73643-handlers-prevent-multiple-runs.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - Prevent running same handler multiple times when included via ``include_role`` (https://github.com/ansible/ansible/issues/73643)

changelogs/fragments/74723-support-wildcard-win_fetch.yml

@@ -1,3 +0,0 @@
-bugfixes:
-- win_fetch - Add support for using file with wildcards in file name.
-  (https://github.com/ansible/ansible/issues/73128)

changelogs/fragments/75063-allow-dev-nul-as-skeleton-for-new-homedir.yml

@@ -1,3 +0,0 @@
-bugfixes:
-  - modules/user.py - Add check for valid directory when creating new user homedir (allows /dev/null as skeleton) (https://github.com/ansible/ansible/issues/75063)
-  

changelogs/fragments/76372-fix-pip-virtualenv-command-parsing.yml

@@ -1,6 +0,0 @@
----
-bugfixes:
-  - >-
-    Fixed `pip` module failure in case of usage quotes for
-    `virtualenv_command` option for the venv command.
-    (https://github.com/ansible/ansible/issues/76372)

changelogs/fragments/78487-galaxy-collections-path-warnings.yml

@@ -1,6 +0,0 @@
----
-minor_changes:
-- >-
-  Add ``GALAXY_COLLECTIONS_PATH_WARNING`` option to disable the warning
-  given by ``ansible-galaxy collection install`` when installing a collection
-  to a path that isn't in the configured collection paths.

changelogs/fragments/79364_replace.yml

@@ -1,2 +0,0 @@
-bugfixes:
-- replace - handle exception when bad escape character is provided in replace (https://github.com/ansible/ansible/issues/79364).

changelogs/fragments/79677-fix-argspec-type-check.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - module/role argument spec - validate the type for options that are None when the option is required or has a non-None default (https://github.com/ansible/ansible/issues/79656).

changelogs/fragments/79734-ansible-test-change-detection.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - "ansible-test local change detection - use ``git merge-base <branch> HEAD`` instead of ``git merge-base --fork-point <branch>`` (https://github.com/ansible/ansible/pull/79734)."

changelogs/fragments/79844-fix-timeout-mounts-linux.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - setup gather_timeout - Fix timeout in get_mounts_facts for linux.

changelogs/fragments/80128-symbolic-modes-X-use-computed.yml

@@ -1,3 +0,0 @@
-bugfixes:
-  - file modules - Make symbolic modes with X use the computed permission, not original file (https://github.com/ansible/ansible/issues/80128)
-  - copy unit tests - Fixing "dir all perms" documentation and formatting for easier reading.

changelogs/fragments/80258-defensive-display-non-utf8.yml

@@ -1,4 +0,0 @@
-bugfixes:
-- Display - Defensively configure writing to stdout and stderr with a custom encoding error handler that will replace invalid characters
-  while providing a deprecation warning that non-utf8 text will result in an error in a future version.
-- module responses - Ensure that module responses are utf-8 adhereing to JSON RFC and expectations of the core code.

changelogs/fragments/80334-reduce-ansible-galaxy-api-calls.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - ansible-galaxy - reduce API calls to servers by fetching signatures only for final candidates.

changelogs/fragments/80406-validate-modules-semantic-markup.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - "validate-modules sanity test - replace semantic markup parsing and validating code with the code from `antsibull-docs-parser 0.2.0 <https://github.com/ansible-community/antsibull-docs-parser/releases/tag/0.2.0>`__ (https://github.com/ansible/ansible/pull/80406)."

changelogs/fragments/80449-fix-symbolic-mode-error-msg.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - file modules - fix validating invalid symbolic modes.

changelogs/fragments/80460-add-symbolic-links-with-dir.yml

@@ -1,3 +0,0 @@
----
-minor_changes:
-  - include_vars - os.walk now follows symbolic links when traversing directories (https://github.com/ansible/ansible/pull/80460)

changelogs/fragments/80476-fix-loop-task-post-validation.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - Fix post-validating looped task fields so the strategy uses the correct values after task execution.

changelogs/fragments/80506-syntax-check-playbook-only.yml

@@ -1,3 +0,0 @@
-bugfixes:
-- syntax check - Limit ``--syntax-check`` to ``ansible-playbook`` only, as that is the only CLI affected by this argument
-  (https://github.com/ansible/ansible/issues/80506)

changelogs/fragments/80520-fix-current-hostname-openbsd.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - The ``hostname`` module now also updates both current and permanent hostname on OpenBSD. Before it only updated the permanent hostname (https://github.com/ansible/ansible/issues/80520).

changelogs/fragments/80605-template-overlay-native-jinja.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - "Properly disable ``jinja2_native`` in the template module when jinja2 override is used in the template (https://github.com/ansible/ansible/issues/80605)"

changelogs/fragments/80648-fix-ansible-galaxy-cache-signatures-bug.yml

@@ -1,3 +0,0 @@
-bugfixes:
-  - ansible-galaxy - fix installing signed collections (https://github.com/ansible/ansible/issues/80648).
-  - ansible-galaxy collection verify - fix verifying signed collections when the keyring is not configured.

changelogs/fragments/80721-ansible-galaxy.yml

@@ -1,2 +0,0 @@
-minor_changes:
-- ansible-galaxy - Remove internal configuration argument ``v3`` (https://github.com/ansible/ansible/pull/80721)

changelogs/fragments/80738-abs-unarachive-src.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - unarchive - fix unarchiving sources that are copied to the remote node using a relative temporory directory path (https://github.com/ansible/ansible/issues/80710).

changelogs/fragments/80880-register-handlers-immediately-if-iterating-handlers.yml

@@ -1,4 +0,0 @@
-bugfixes:
-- "From issue https://github.com/ansible/ansible/issues/80880, when notifying a
-  handler from another handler, handler notifications must be registered
-  immediately as the flush_handler call is not recursive."

changelogs/fragments/80887-dnf5-api-change.yml

@@ -1,3 +0,0 @@
-bugfixes:
-- dnf5 - Update dnf5 module to handle API change for setting the download directory
-  (https://github.com/ansible/ansible/issues/80887)

changelogs/fragments/80943-ansible-galaxy-collection-subdir-install.yml

@@ -1,3 +0,0 @@
-bugfixes:
-- ansible-galaxy - Fix variable type error when installing subdir collections
-  (https://github.com/ansible/ansible/issues/80943)

changelogs/fragments/80968-replace-deprecated-ast-attr.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - Fix ``ast`` deprecation warnings for ``Str`` and ``value.s`` when using Python 3.12.

changelogs/fragments/80985-fix-smgl-family-mapping.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - distribution facts - fix Source Mage family mapping

changelogs/fragments/81005-use-overlay-overrides.yml

@@ -1,2 +0,0 @@
-bugfixes:
-- templating - In the template action and lookup, use local jinja2 environment overlay overrides instead of mutating the templars environment

changelogs/fragments/81029-connection-types.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - "paramiko_ssh, psrp, and ssh connection plugins - ensure that all values for options that should be strings are actually converted to strings (https://github.com/ansible/ansible/pull/81029)."

changelogs/fragments/81064-daemonize-fixes.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - "``ansible.module_utils.service`` - fix inter-process communication in ``daemonize()``"

changelogs/fragments/81082-deprecated-importlib-abc.yml

@@ -1,5 +0,0 @@
----
-minor_changes:
-  - Use ``importlib.resources.abc.TraversableResources`` instead of deprecated
-    ``importlib.abc.TraversableResources`` where available
-    (https:/github.com/ansible/ansible/pull/81082).

changelogs/fragments/81104-inventory-script-plugin-raise-execution-error.yml

@@ -1,2 +0,0 @@
-bugfixes:
-- Inventory scripts parser not treat exception when getting hostsvar (https://github.com/ansible/ansible/issues/81103)

changelogs/fragments/81319-cloudstack-test-container-bump-version.yml

@@ -1,2 +0,0 @@
-minor_changes:
-  - ansible-test - Updated the CloudStack test container to version 1.6.1.

changelogs/fragments/83642-fix-sanity-ignore-for-uri.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - uri - mark ``url`` as required (https://github.com/ansible/ansible/pull/83642).

changelogs/fragments/83643-fix-sanity-ignore-for-copy.yml

@@ -0,0 +1,3 @@
+minor_changes:
+  - copy - parameter ``local_follow`` was incorrectly documented as having default value ``True`` (https://github.com/ansible/ansible/pull/83643).
+  - copy - fix sanity test failures (https://github.com/ansible/ansible/pull/83643).

changelogs/fragments/83690-get_url-content-disposition-filename.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - get_url - fix honoring ``filename`` from the ``content-disposition`` header even when the type is ``inline`` (https://github.com/ansible/ansible/issues/83690)

changelogs/fragments/83700-enable-file-disable-diff.yml

@@ -0,0 +1,2 @@
+minor_changes:
+  - file - enable file module to disable diff_mode (https://github.com/ansible/ansible/issues/80817).

changelogs/fragments/83965-action-groups-schema.yml

@@ -0,0 +1,2 @@
+minor_changes:
+  - "runtime-metadata sanity test - improve validation of ``action_groups`` (https://github.com/ansible/ansible/pull/83965)."

changelogs/fragments/84008-additional-logging.yml

@@ -0,0 +1,3 @@
+minor_changes:
+  - Added a -vvvvv log message indicating when a host fails to produce output within the timeout period.
+  - SSH Escalation-related -vvv log messages now include the associated host information.

changelogs/fragments/84019-ignore_unreachable-loop.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - Fix returning 'unreachable' for the overall task result. This prevents false positives when a looped task has unignored unreachable items (https://github.com/ansible/ansible/issues/84019).

changelogs/fragments/84149-add-flush-cache-for-adhoc-commands.yml

@@ -0,0 +1,3 @@
+minor_changes:
+- >
+  ansible, ansible-console, ansible-pull - add --flush-cache option (https://github.com/ansible/ansible/issues/83749).

changelogs/fragments/84229-windows-server-2025.yml

@@ -0,0 +1,4 @@
+minor_changes:
+  - >-
+    Windows - Add support for Windows Server 2025 to Ansible and as an ``ansible-test``
+    remote target - https://github.com/ansible/ansible/issues/84229

changelogs/fragments/CleansingNodeVisitor-removal.yml

@@ -1,2 +0,0 @@
-minor_changes:
-  - Remove the ``CleansingNodeVisitor`` class and its usage due to the templating changes that made it superfluous. Also simplify the ``Conditional`` class.

changelogs/fragments/a-g-col-install-directory-with-trailing-sep.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - ansible-galaxy - fix installing collections from directories that have a trailing path separator (https://github.com/ansible/ansible/issues/77803).

changelogs/fragments/a-g-col-prevent-reinstalling-satisfied-req.yml

@@ -1,7 +0,0 @@
-bugfixes:
-- >-
-  ``ansible-galaxy`` now considers all collection paths when identifying which collection requirements are already installed.
-  Use the ``COLLECTIONS_PATHS`` and ``COLLECTIONS_SCAN_SYS_PATHS`` config options to modify these.
-  Previously only the install path was considered when resolving the candidates.
-  The install path will remain the only one potentially modified.
-  (https://github.com/ansible/ansible/issues/79767, https://github.com/ansible/ansible/issues/81163)

changelogs/fragments/ansible-galaxy-server-timeout.yml

@@ -1,2 +0,0 @@
-minor_changes:
-  - Add a general ``GALAXY_SERVER_TIMEOUT`` config option for distribution servers (https://github.com/ansible/ansible/issues/79833).

changelogs/fragments/ansible-runtime-metadata-removal-date.yml

@@ -1,2 +0,0 @@
-minor_changes:
-  - Record ``removal_date`` in runtime metadata as a string instead of a date.

changelogs/fragments/ansible-test-added-fedora-38.yml

@@ -1,3 +0,0 @@
-minor_changes:
-  - ansible-test - Add Fedora 38 remote.
-  - ansible-test - Add Fedora 38 container.

changelogs/fragments/ansible-test-argcomplete-3.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - ansible-test - Add support for ``argcomplete`` version 3.

changelogs/fragments/ansible-test-atexit.yml

@@ -1,2 +0,0 @@
-minor_changes:
-  - ansible-test - Use a context manager to perform cleanup at exit instead of using the built-in ``atexit`` module.

changelogs/fragments/ansible-test-default-containers.yml

@@ -1,2 +0,0 @@
-minor_changes:
-  - ansible-test - Update the ``default`` containers.

changelogs/fragments/ansible-test-deprecated-cleanup.yml

@@ -1,5 +0,0 @@
-minor_changes:
-  - ansible-test - Removed the deprecated ``--docker-no-pull`` option.
-  - ansible-test - Removed the deprecated ``--no-pip-check`` option.
-  - ansible-test - Removed the deprecated ``foreman`` test plugin.
-  - ansible-test - Removed the deprecated ``govcsim`` support from the ``vcenter`` test plugin.

changelogs/fragments/ansible-test-distro-containers.yml

@@ -1,2 +0,0 @@
-minor_changes:
-  - ansible-test - The openSUSE test container has been updated to openSUSE Leap 15.5.

changelogs/fragments/ansible-test-explain-traceback.yml

@@ -1,3 +0,0 @@
-bugfixes:
-  - ansible-test - Fix several possible tracebacks when using the ``-e`` option with sanity tests.
-  - ansible-test - Remove redundant warning about missing programs before attempting to execute them.

changelogs/fragments/ansible-test-fedora-37.yml

@@ -1,3 +0,0 @@
-minor_changes:
-  - ansible-test - Remove Fedora 37 remote support.
-  - ansible-test - Remove Fedora 37 test container.

changelogs/fragments/ansible-test-fix-command-traceback.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - ansible-test - Fix traceback that occurs after an interactive command fails.

changelogs/fragments/ansible-test-freebsd-bootstrap-setuptools.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - ansible-test - When bootstrapping remote FreeBSD instances, use the OS packaged ``setuptools`` instead of installing the latest version from PyPI.

changelogs/fragments/ansible-test-import-sanity-fix.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - ansible-test - The ``import`` sanity test now checks the collection loader for remote-only Python support when testing ansible-core.

changelogs/fragments/ansible-test-long-timeout-fix.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - ansible-test - Fix handling of timeouts exceeding one day.

changelogs/fragments/ansible-test-minimum-setuptools.yml

@@ -1,2 +0,0 @@
-minor_changes:
-  - The minimum required ``setuptools`` version is now 66.1.0, as it is the oldest version to support Python 3.12.

changelogs/fragments/ansible-test-nios-container.yml

@@ -1,2 +1,2 @@
 minor_changes:
-  - ansible-test - Update the ``nios-test-container`` to version 2.0.0, which supports API version 2.9.
+  - ansible-test - Update ``nios-test-container`` to version 6.0.0.

changelogs/fragments/ansible-test-probe-error-handling.yml

@@ -0,0 +1,3 @@
+minor_changes:
+  - ansible-test - Improve container runtime probe error handling.
+    When unexpected probe output is encountered, an error with more useful debugging information is provided.

changelogs/fragments/ansible-test-pylint-fix.yml

@@ -0,0 +1,4 @@
+bugfixes:
+  - ansible-test - Enable the ``sys.unraisablehook`` work-around for the ``pylint`` sanity test on Python 3.11.
+    Previously the work-around was only enabled for Python 3.12 and later.
+    However, the same issue has been discovered on Python 3.11.

changelogs/fragments/ansible-test-pylint-update.yml

@@ -1,3 +0,0 @@
-bugfixes:
-  - ansible-test - Update ``pylint`` to 2.17.2 to resolve several possible false positives.
-  - ansible-test - Update ``pylint`` to 2.17.3 to resolve several possible false positives.

changelogs/fragments/ansible-test-pytest-forked.yml

@@ -1,5 +0,0 @@
-minor_changes:
-  - ansible-test - Replace the ``pytest-forked`` pytest plugin with a custom plugin.
-bugfixes:
-  - ansible-test - Unit tests now report warnings generated during test runs.
-                   Previously only warnings generated during test collection were reported.

changelogs/fragments/ansible-test-python-3.12.yml

@@ -1,4 +0,0 @@
-minor_changes:
-  - ansible-test - Add support for testing with Python 3.12.
-  - ansible-test - Update pip to ``23.1.2`` and setuptools to ``67.7.2``.
-  - Add ``python3.12`` to the default ``INTERPRETER_PYTHON_FALLBACK`` list.

changelogs/fragments/ansible-test-pyyaml-build.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - ansible-test - Pre-build a PyYAML wheel before installing requirements to avoid a potential Cython build failure.

changelogs/fragments/ansible-test-remotes.yml

@@ -0,0 +1,2 @@
+minor_changes:
+  - ansible-test - Replace remote FreeBSD 13.3 with 13.4.

changelogs/fragments/ansible-test-remove-old-rhel-remotes.yml

@@ -1,2 +0,0 @@
-minor_changes:
-  - "ansible-test - Removed test remotes: rhel/8.7, rhel/9.1"

changelogs/fragments/ansible-test-remove-ubuntu-2004.yml

@@ -1,2 +0,0 @@
-minor_changes:
-  - ansible-test - Removed Ubuntu 20.04 LTS image from the `--remote` option.