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

.azure-pipelines/azure-pipelines.yml

@@ -68,9 +68,20 @@ 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:
@@ -79,14 +90,14 @@ stages:
           targets:
             - name: macOS 14.3
               test: macos/14.3
-            - name: RHEL 9.3 py39
+            - name: RHEL 9.4 py39
-              test: rhel/9.3@3.9
+              test: rhel/9.4@3.9
-            - name: RHEL 9.3 py311
+            - name: RHEL 9.4 py312
-              test: rhel/9.3@3.11
+              test: rhel/9.4@3.12
-            - name: FreeBSD 13.3
+            - name: FreeBSD 13.4
-              test: freebsd/13.3
+              test: freebsd/13.4
-            - name: FreeBSD 14.0
+            - name: FreeBSD 14.1
-              test: freebsd/14.0
+              test: freebsd/14.1
           groups:
             - 1
             - 2
@@ -95,12 +106,12 @@ stages:
           targets:
             - name: macOS 14.3
               test: macos/14.3
-            - name: RHEL 9.3
+            - name: RHEL 9.4
-              test: rhel/9.3
+              test: rhel/9.4
-            - name: FreeBSD 13.3
+            - name: FreeBSD 13.4
-              test: freebsd/13.3
+              test: freebsd/13.4
-            - name: FreeBSD 14.0
+            - name: FreeBSD 14.1
-              test: freebsd/14.0
+              test: freebsd/14.1
           groups:
             - 3
             - 4
@@ -108,44 +119,44 @@ stages:
       - template: templates/matrix.yml  # context/controller (ansible-test container management)
         parameters:
           targets:
-            - name: Alpine 3.19
+            - name: Alpine 3.20
-              test: alpine/3.19
+              test: alpine/3.20
-            - name: Fedora 39
+            - name: Fedora 40
-              test: fedora/39
+              test: fedora/40
-            - name: RHEL 9.3
+            - name: RHEL 9.4
-              test: rhel/9.3
+              test: rhel/9.4
-            - name: Ubuntu 22.04
+            - name: Ubuntu 24.04
-              test: ubuntu/22.04
+              test: ubuntu/24.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.19
+            - name: Alpine 3.20
-              test: alpine319
+              test: alpine320
-            - name: Fedora 39
+            - name: Fedora 40
-              test: fedora39
+              test: fedora40
-            - 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.19
+            - name: Alpine 3.20
-              test: alpine319
+              test: alpine320
-            - name: Fedora 39
+            - name: Fedora 40
-              test: fedora39
+              test: fedora40
-            - name: Ubuntu 22.04
+            - name: Ubuntu 24.04
-              test: ubuntu2204
+              test: ubuntu2404
           groups:
             - 3
             - 4
@@ -158,7 +169,6 @@ stages:
           nameFormat: Python {0}
           testFormat: galaxy/{0}/1
           targets:
-            - test: '3.10'
             - test: 3.11
             - test: 3.12
             - test: 3.13
@@ -170,7 +180,6 @@ stages:
           nameFormat: Python {0}
           testFormat: generic/{0}/1
           targets:
-            - test: '3.10'
             - test: 3.11
             - test: 3.12
             - test: 3.13
@@ -183,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:
@@ -195,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

.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,11 +4,14 @@ Hi! Nice to see you here!
 
 ## QUESTIONS ?
 
-Please see the [Community Guide](https://docs.ansible.com/ansible/latest/community/index.html) for information on
+If you have questions about anything related to Ansible, get in touch with us!
-how to ask questions on the [mailing lists](https://docs.ansible.com/ansible/latest/community/communication.html#mailing-list-information) and IRC.
+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,
+The [Community Guide](https://docs.ansible.com/ansible/devel/community/index.html) also explains how to contribute
-but both IRC and the mailing list are very helpful places for those things, as the community page explains best.
+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 ?
 
@@ -17,11 +20,11 @@ By contributing to this project you agree to the [Developer Certificate of Origi
 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.
 
 The Ansible project accepts contributions through GitHub pull requests.
-Please review the [Community Guide](https://docs.ansible.com/ansible/latest/community/index.html) for more information on contributing to Ansible.
+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.

.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 🤷
 
 
@@ -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
 
@@ -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 🤷
 
 
@@ -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/RELEASE_NAMES.txt

@@ -1,3 +1,4 @@
+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

.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,11 +1,10 @@
 include COPYING
-include bin/*
 include changelogs/CHANGELOG*.rst
 include changelogs/changelog.yaml
 include licenses/*.txt
 include requirements.txt
 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://docs.ansible.com/ansible/devel/community/communication.html#working-groups),
-  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/devel/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

changelogs/changelog.yaml

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

changelogs/fragments/72321_git.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-- git - check if git version is available or not before using it for comparison (https://github.com/ansible/ansible/issues/72321).

changelogs/fragments/82307-handlers-lockstep-linear-fix.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - Fix handlers not being executed in lockstep using the linear strategy in some cases (https://github.com/ansible/ansible/issues/82307)

changelogs/fragments/82535-properly-quote-shell.yml

@@ -1,2 +0,0 @@
-bugfixes:
-- shell plugin - properly quote all needed components of shell commands (https://github.com/ansible/ansible/issues/82535)

changelogs/fragments/82671-ansible-doc-role-examples.yml

@@ -1,2 +0,0 @@
-minor_changes:
-  - "ansible-doc - show examples in role entrypoint argument specs (https://github.com/ansible/ansible/pull/82671)."

changelogs/fragments/82831_countme_yum_repository.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - support the countme option when using yum_repository

changelogs/fragments/82878-fetch-dest-is-dir.yml

@@ -1,4 +0,0 @@
-bugfixes:
-- >-
-    fetch - add error message when using ``dest`` with a trailing slash that becomes a local directory -
-    https://github.com/ansible/ansible/issues/82878

changelogs/fragments/82941.yml

@@ -1,5 +0,0 @@
----
-removed_features:
-  - paramiko_ssh - removed deprecated ssh_extra_args from the paramiko_ssh connection plugin (https://github.com/ansible/ansible/issues/82941).
-  - paramiko_ssh - removed deprecated ssh_common_args from the paramiko_ssh connection plugin (https://github.com/ansible/ansible/issues/82940).
-  - paramiko_ssh - removed deprecated ssh_args from the paramiko_ssh connection plugin (https://github.com/ansible/ansible/issues/82939).

changelogs/fragments/82946.yml

@@ -1,3 +0,0 @@
----
-removed_features:
-  - play_context - remove deprecated PlayContext.verbosity property (https://github.com/ansible/ansible/issues/82945).

changelogs/fragments/82947.yml

@@ -1,3 +0,0 @@
----
-removed_features:
-  - loader - remove deprecated non-inclusive words (https://github.com/ansible/ansible/issues/82947).

changelogs/fragments/83031.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-  - lookup - Fixed examples of csv lookup plugin (https://github.com/ansible/ansible/issues/83031).

changelogs/fragments/83155-ansible-doc-paragraphs.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - "ansible-doc - format top-level descriptions with multiple paragraphs as multiple paragraphs, instead of concatenating them (https://github.com/ansible/ansible/pull/83155)."

changelogs/fragments/83327.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-  - fixed unit test test_borken_cowsay to address mock not been properly applied when existing unix system already have cowsay installed.

changelogs/fragments/83331.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-  - facts - add facts about x86_64 flags to detect microarchitecture (https://github.com/ansible/ansible/issues/83331).

changelogs/fragments/83392-fix-memory-issues-handlers.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - Fix rapid memory usage growth when notifying handlers using the ``listen`` keyword (https://github.com/ansible/ansible/issues/83392)

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/PowerShell-AddType-temp.yml

@@ -1,7 +0,0 @@
-bugfixes:
-- >-
-  powershell - Implement more robust deletion mechanism for C# code compilation
-  temporary files. This should avoid scenarios where the underlying temporary
-  directory may be temporarily locked by antivirus tools or other IO problems.
-  A failure to delete one of these temporary directories will result in a
-  warning rather than an outright failure.

changelogs/fragments/action-plugin-docs-sidecar.yml

@@ -1,2 +0,0 @@
-bugfixes:
-- ansible-test action-plugin-docs - Fix to check for sidecar documentation for action plugins

changelogs/fragments/add_systemd_facts.yml

@@ -1,2 +0,0 @@
-minor_changes:
-  - facts - add systemd version and features

changelogs/fragments/ansible-config-validate.yml

@@ -1,2 +0,0 @@
-minor_changes:
-  - ansible-config has new 'validate' option to find mispelled/forgein configurations in ini file or environment variables.

changelogs/fragments/ansible-doc-color.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-  - ansible-doc - make colors configurable.

changelogs/fragments/ansible-doc-inicate.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - ansible-doc - fixed "inicates" typo in output

changelogs/fragments/ansible-drop-python-3.7.yml

@@ -1,2 +0,0 @@
-minor_changes:
-  - The minimum supported Python version on targets is now Python 3.8.

changelogs/fragments/ansible-galaxy-role-install-symlink.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - ansible-galaxy role install - fix symlinks (https://github.com/ansible/ansible/issues/82702, https://github.com/ansible/ansible/issues/81965).

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

@@ -1,2 +0,0 @@
-minor_changes:
-  - ansible-test - Update ``base`` and ``default`` containers to omit Python 3.7.

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

@@ -1,2 +0,0 @@
-minor_changes:
-  - ansible-test - Update ``coverage`` to version 7.5.3.

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-http-test-container-update.yml

@@ -1,2 +0,0 @@
-minor_changes:
-  - ansible-test - Update ``http-test-container`` to version 3.0.0.

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

@@ -0,0 +1,2 @@
+minor_changes:
+  - 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-pypi-test-container-update.yml

@@ -1,2 +0,0 @@
-minor_changes:
-  - ansible-test - Update ``pypi-test-container`` to version 3.0.0.

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-update.yml

@@ -0,0 +1,5 @@
+minor_changes:
+  - ansible-test - Update ``pylint`` sanity test to use version 3.3.1.
+  - ansible-test - Default to Python 3.13 in the ``base`` and ``default`` containers.
+  - ansible-test - Disable the ``deprecated-`` prefixed ``pylint`` rules as their results vary by Python version.
+  - ansible-test - Update the ``base`` and ``default`` containers.

changelogs/fragments/ansible-test-utility-container-update.yml

@@ -1,2 +0,0 @@
-minor_changes:
-  - ansible-test - Update ``ansible-test-utility-container`` to version 3.0.0.

changelogs/fragments/ansible_connection_path.yml

@@ -1,8 +0,0 @@
-bugfixes:
-  - persistent connection plugins - The correct Ansible persistent connection helper is now always used.
-    Previously, the wrong script could be used, depending on the value of the ``PATH`` environment variable.
-    As a result, users were sometimes required to set ``ANSIBLE_CONNECTION_PATH`` to use the correct script.
-deprecated_features:
-  - persistent connection plugins - The ``ANSIBLE_CONNECTION_PATH`` config option no longer has any effect, and will be removed in a future release.
-breaking_changes:
-  - persistent connection plugins - The ``ANSIBLE_CONNECTION_PATH`` config option no longer has any effect.

changelogs/fragments/ansible_managed_restore.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - ansible_managed restored it's 'templatability' by ensuring the possible injection routes are cut off earlier in the process.

changelogs/fragments/apk_package_facts.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-  - package_facts - apk fix when cache is empty (https://github.com/ansible/ansible/issues/83126).

changelogs/fragments/apt_cache.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-  - apt_* - add more info messages raised while updating apt cache (https://github.com/ansible/ansible/issues/77941).

changelogs/fragments/assemble.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-  - assemble - update argument_spec with 'decrypt' option which is required by action plugin (https://github.com/ansible/ansible/issues/80840).

changelogs/fragments/become-runas-system-deux.yml

@@ -0,0 +1,3 @@
+bugfixes:
+  - >-
+    runas become - Fix up become logic to still get the SYSTEM token with the most privileges when running as SYSTEM.

changelogs/fragments/buildroot.yml

@@ -0,0 +1,3 @@
+---
+bugfixes:
+  - user - Create Buildroot subclass as alias to Busybox (https://github.com/ansible/ansible/issues/83665).

changelogs/fragments/cleanup-outdated-galaxy-install-info.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - ansible-galaxy collection install - remove old installation info when installing collections (https://github.com/ansible/ansible/issues/83182).

changelogs/fragments/compat_removal.yml

@@ -0,0 +1,3 @@
+---
+removed_features:
+  - removed deprecated pycompat24 and compat.importlib.

changelogs/fragments/config.yml

@@ -0,0 +1,3 @@
+---
+removed_features:
+  - Remove deprecated plural form of collection path (https://github.com/ansible/ansible/pull/84156).

changelogs/fragments/config_init_fix.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - ansible-config will now properly template defaults before dumping them.

changelogs/fragments/correct-callback-fqcn-old-style-action-invocation.yml

@@ -1,3 +0,0 @@
-bugfixes:
-  - Fix the task attribute ``resolved_action`` to show the FQCN instead of ``None`` when ``action`` or ``local_action`` is used in the playbook.
-  - Fix using ``module_defaults`` with ``local_action``/``action`` (https://github.com/ansible/ansible/issues/81905).

changelogs/fragments/cron_err.yml

@@ -0,0 +1,3 @@
+---
+minor_changes:
+  - cron - Provide additional error information while writing cron file (https://github.com/ansible/ansible/issues/83223).

changelogs/fragments/cve-2024-8775.yml

@@ -0,0 +1,5 @@
+security_fixes:
+  - task result processing - Ensure that action-sourced result masking (``_ansible_no_log=True``)
+    is preserved. (CVE-2024-8775)
+  - include_vars action - Ensure that result masking is correctly requested when vault-encrypted
+    files are read. (CVE-2024-8775)

changelogs/fragments/darwin_facts.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-  - Darwin - add unit tests for Darwin hardware fact gathering.

changelogs/fragments/debconf_empty_password.yml

@@ -0,0 +1,3 @@
+---
+bugfixes:
+  - debconf - set empty password values (https://github.com/ansible/ansible/issues/83214).

changelogs/fragments/deprecated.yml

@@ -0,0 +1,3 @@
+---
+minor_changes:
+  - docs - add collection name in message from which the module is being deprecated (https://github.com/ansible/ansible/issues/84116).

changelogs/fragments/dnf-installroot-substitutions.yml

@@ -1,3 +0,0 @@
-bugfixes:
-  - dnf - honor installroot for ``cachedir``, ``logdir`` and ``persistdir``
-  - dnf - perform variable substitutions in ``logdir`` and ``persistdir``

changelogs/fragments/dnf5-api-breaks.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - dnf5 - replace removed API calls

changelogs/fragments/dnf5-enable-disable-plugins.yml

@@ -1,2 +0,0 @@
-minor_changes:
-  - dnf5 - implement ``enable_plugin`` and ``disable_plugin`` options

changelogs/fragments/dnf5-plugins-compat.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - "dnf5 - fix traceback when ``enable_plugins``/``disable_plugins`` is used on ``python3-libdnf5`` versions that do not support this functionality"

changelogs/fragments/dnf_cache_path.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-  - dnf - Substitute variables in DNF cache path (https://github.com/ansible/ansible/pull/80094).

changelogs/fragments/enabled_runtime.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-  - systemd - extend systemctl is-enabled check to handle "enabled-runtime" (https://github.com/ansible/ansible/pull/77754).

changelogs/fragments/file_hardlink.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-  - file - retrieve the link's full path when hard linking a soft link with follow (https://github.com/ansible/ansible/issues/33911).

changelogs/fragments/file_simplify.yml

@@ -0,0 +1,3 @@
+---
+minor_changes:
+  - file - make code more readable and simple.

changelogs/fragments/find-checksum.yml

@@ -0,0 +1,2 @@
+minor_changes:
+  - find - add a checksum_algorithm parameter to specify which type of checksum the module will return

changelogs/fragments/fix-ansible-galaxy-ignore-certs.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - Fix disabling SSL verification when installing collections and roles from git repositories. If ``--ignore-certs`` isn't provided, the value for the ``GALAXY_IGNORE_CERTS`` configuration option will be used (https://github.com/ansible/ansible/issues/83326).

changelogs/fragments/fix-ipv6-pattern.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - Fix ipv6 pattern bug in lib/ansible/parsing/utils/addresses.py (https://github.com/ansible/ansible/issues/84237)

changelogs/fragments/fix-module-utils-facts-timeout.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - Use the requested error message in the ansible.module_utils.facts.timeout timeout function instead of hardcoding one.

changelogs/fragments/fix_errors.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - Errors now preserve stacked error messages even when YAML is involved.

changelogs/fragments/fix_log_verbosity.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - ensure we have logger before we log when we have increased verbosity.

changelogs/fragments/freebsd_disk_regex.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-  - freebsd - update disk and slices regex for fact gathering (https://github.com/ansible/ansible/pull/82081).

changelogs/fragments/freebsd_facts_refactor.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-  - freebsd - refactor dmidecode fact gathering code for simplicity.

changelogs/fragments/freebsd_service.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-  - service - fix order of CLI arguments on FreeBSD (https://github.com/ansible/ansible/pull/81377).

changelogs/fragments/gather-s390-sysinfo.yml

@@ -1,2 +0,0 @@
-minor_changes:
-- fact gathering - Gather /proc/sysinfo facts on s390 Linux on Z

changelogs/fragments/libvirt_lxc.yml

@@ -0,0 +1,3 @@
+---
+bugfixes:
+  - base.yml - deprecated libvirt_lxc_noseclabel config.

changelogs/fragments/listify.yml

@@ -1,3 +0,0 @@
----
-removed_features:
-  - utils/listify - remove deprecated 'loader' argument from listify_lookup_plugin_terms API (https://github.com/ansible/ansible/issues/82949).

changelogs/fragments/mask_me.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-  - systemd_service - handle mask operation failure (https://github.com/ansible/ansible/issues/81649).

changelogs/fragments/no-return.yml

@@ -0,0 +1,2 @@
+minor_changes:
+  - module_utils - Add ``NoReturn`` type annotations to functions which never return.

changelogs/fragments/os_family.yml

@@ -0,0 +1,3 @@
+---
+bugfixes:
+  - facts - skip if distribution file path is directory, instead of raising error (https://github.com/ansible/ansible/issues/84006).

changelogs/fragments/package-dnf-action-plugins-facts-fail-msg.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - "``package``/``dnf`` action plugins - provide the reason behind the failure to gather the ``ansible_pkg_mgr`` fact to identify the package backend"

changelogs/fragments/package_facts_aliases.yml

@@ -1,2 +0,0 @@
-minor_changes:
-  - package_facts module now supports using aliases for supported package managers, for example managers=yum or managers=dnf will resolve to using the underlying rpm.

changelogs/fragments/package_facts_fix.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - package_facts module when using 'auto' will return the first package manager found that provides an output, instead of just the first one, as this can be foreign and not have any packages.