Merge branch '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
 
@@ -59,6 +59,7 @@ stages:
             - test: '3.10'
             - test: 3.11
             - test: 3.12
+            - test: 3.13
   - stage: Windows
     dependsOn: []
     jobs:
@@ -67,9 +68,16 @@ 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
   - stage: Remote
     dependsOn: []
     jobs:
@@ -78,14 +86,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
               test: freebsd/13.3
-            - name: FreeBSD 14.0
+            - name: FreeBSD 14.1
-              test: freebsd/14.0
+              test: freebsd/14.1
           groups:
             - 1
             - 2
@@ -94,12 +102,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
               test: freebsd/13.3
-            - name: FreeBSD 14.0
+            - name: FreeBSD 14.1
-              test: freebsd/14.0
+              test: freebsd/14.1
           groups:
             - 3
             - 4
@@ -107,44 +115,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
@@ -157,9 +165,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:
@@ -168,9 +176,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: []
@@ -180,9 +188,16 @@ 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
   - stage: Incidental
     dependsOn: []
     jobs:
@@ -192,8 +207,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

.github/CONTRIBUTING.md

@@ -4,9 +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 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 ?
 
@@ -14,15 +19,18 @@ 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.
+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!
 

.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

.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

bin/ansible-connection

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

changelogs/fragments/42960_vault_password.yml

@@ -0,0 +1,3 @@
+---
+bugfixes:
+- vault - handle vault password file value when it is directory (https://github.com/ansible/ansible/issues/42960).

changelogs/fragments/46314.yml

@@ -0,0 +1,3 @@
+---
+bugfixes:
+  - apt - report changed=True when some packages are being removed (https://github.com/ansible/ansible/issues/46314).

changelogs/fragments/46742-atomic_move-fix-setgid.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - atomic_move - fix using the setgid bit on the parent directory when creating files (https://github.com/ansible/ansible/issues/46742, https://github.com/ansible/ansible/issues/67177).

changelogs/fragments/62151-loop_control-until.yml

@@ -0,0 +1,2 @@
+minor_changes:
+  - loop_control - add a break_when option to to break out of a task loop early based on Jinja2 expressions (https://github.com/ansible/ansible/issues/83442).

changelogs/fragments/64092-get_url_verify_tmpsrc_checksum.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - get_url - Verify checksum using tmpsrc, not dest (https://github.com/ansible/ansible/pull/64092)

changelogs/fragments/72321_git.yml

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

changelogs/fragments/81770-add-uid-guid-minmax-keys.yml

@@ -0,0 +1,3 @@
+minor_changes:
+    - Add ``uid_min``, ``uid_max`` to the user plugin to overwrite the defaults provided by the ``/etc/login.defs`` file (https://github.com/ansible/ansible/pull/81770).
+    - Add ``gid_min``, ``gid_max`` to the group plugin to overwrite the defaults provided by the ``/etc/login.defs`` file (https://github.com/ansible/ansible/pull/81770).

changelogs/fragments/82075.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - addressed issue of trailing text been ignored, non-ASCII characters are parsed, enhance white space handling and fixed overly permissive issue of human_to_bytes filter(https://github.com/ansible/ansible/issues/82075)

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

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

changelogs/fragments/82490_creating_user_dir_using_tilde_always_reports_changed.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - fixed the issue of creating user directory using tilde(~) always reported "changed".(https://github.com/ansible/ansible/issues/82490)

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

@@ -0,0 +1,2 @@
+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

@@ -0,0 +1,2 @@
+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

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

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

@@ -0,0 +1,2 @@
+bugfixes:
+  - "linear strategy: fix handlers included via ``include_tasks`` handler to be executed in lockstep (https://github.com/ansible/ansible/issues/83019)"

changelogs/fragments/83031.yml

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

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

@@ -0,0 +1,2 @@
+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/83235-copy-module-update-mtime.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - copy - mtime/atime not updated. Fix now update mtime/atime(https://github.com/ansible/ansible/issues/83013)

changelogs/fragments/83294-meta-host_pinned-affinity.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - Fix for ``meta`` tasks breaking host/fork affinity with ``host_pinned`` strategy (https://github.com/ansible/ansible/issues/83294)

changelogs/fragments/83327.yml

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

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

changelogs/fragments/83373-dnf5-wildcard.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - dnf, dnf5 - fix for installing a set of packages by specifying them using a wildcard character (https://github.com/ansible/ansible/issues/83373)

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

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

changelogs/fragments/83406-dnf-fix-arch-cmp.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - dnf - fix an issue where two packages of the same ``evr`` but different arch failed to install (https://github.com/ansible/ansible/issues/83406)

changelogs/fragments/83447-end_host-rescue-rc.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - "``end_host`` - fix incorrect return code when executing ``end_host`` in the ``rescue`` section (https://github.com/ansible/ansible/issues/83447)"

changelogs/fragments/83457-service_facts-openbsd-dont-crash-in-equals.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - service_facts - don't crash if OpenBSD rcctl variable contains '=' character (https://github.com/ansible/ansible/issues/83457)

changelogs/fragments/83469-http-test-container.yml

@@ -0,0 +1,2 @@
+minor_changes:
+  - "ansible-test - update HTTP test container to 3.2.0 (https://github.com/ansible/ansible/pull/83469)."

changelogs/fragments/83480-fix-support-discard.yml

@@ -0,0 +1,6 @@
+---
+bugfixes:
+  - facts - `support_discard` now returns `0` if either `discard_granularity`
+    or `discard_max_hw_bytes` is zero; otherwise it returns the value of
+    `discard_granularity`, as before
+    (https://github.com/ansible/ansible/pull/83480).

changelogs/fragments/83498-command-tb-env.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - Fix a traceback when an environment variable contains certain special characters (https://github.com/ansible/ansible/issues/83498)

changelogs/fragments/83508_mount_facts.yml

@@ -0,0 +1,2 @@
+minor_changes:
+  - Add a new mount_facts module to support gathering information about mounts that are excluded by default fact gathering.

changelogs/fragments/83530-validate-modules-casing.yml

@@ -0,0 +1,2 @@
+minor_changes:
+  - "validate-modules sanity test - reject option/aliases names that are identical up to casing but belong to different options (https://github.com/ansible/ansible/pull/83530)."

changelogs/fragments/83540-update_disto_version.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - distro package - update the distro package version from 1.8.0 to 1.9.0  (https://github.com/ansible/ansible/issues/82935)

changelogs/fragments/83541-add-sl-micro-suse-family.yaml

@@ -0,0 +1,2 @@
+minor_changes:
+- distribution.py - Added SL-Micro in Suse OS Family. (https://github.com/ansible/ansible/pull/83541)

changelogs/fragments/83575-fix-sanity-ignore-for-find.yml

@@ -0,0 +1,2 @@
+minor_changes:
+  - find - change the datatype of ``elements`` to ``path`` in option ``paths`` (https://github.com/ansible/ansible/pull/83575).

changelogs/fragments/83599-validate-modules-aliases.yml

@@ -0,0 +1,3 @@
+minor_changes:
+  - "validate-modules sanity test - detect if names of an option (option name + aliases) do not match between argument spec and documentation
+     (https://github.com/ansible/ansible/issues/83598, https://github.com/ansible/ansible/pull/83599)."

changelogs/fragments/83601-debconf-normalize-bools.yml

@@ -0,0 +1,3 @@
+---
+bugfixes:
+  - debconf - fix normalization of value representation for boolean vtypes in new packages (https://github.com/ansible/ansible/issues/83594)

changelogs/fragments/83619-loop-label-register.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - Fix an issue where registered variable was not available for templating in ``loop_control.label`` on skipped looped tasks (https://github.com/ansible/ansible/issues/83619)

changelogs/fragments/83716-enable-subkey-fingerprint-validation-in-rpm-key-module.yml

@@ -0,0 +1,4 @@
+---
+minor_changes:
+  - rpm_key - allow validation of gpg key with a subkey fingerprint
+  - rpm_key - enable gpg validation that requires presence of multiple fingerprints

changelogs/fragments/83755-ini-new-interpolation-option.yml

@@ -0,0 +1,2 @@
+minor_changes:
+  - ini lookup - add new ``interpolation`` option (https://github.com/ansible/ansible/issues/83755)

changelogs/fragments/83803-collection-import-poll-interval.yml

@@ -0,0 +1,4 @@
+minor_changes:
+- >-
+  ``ansible-galaxy collection publish`` - add configuration options for the initial poll interval
+  and the exponential when checking the import status of a collection, since the default is relatively slow.

changelogs/fragments/83831-runtime-metadata-fix.yml

@@ -0,0 +1,3 @@
+bugfixes:
+  - "runtime-metadata sanity test - do not crash on deprecations if ``galaxy.yml`` contains an empty ``version`` field (https://github.com/ansible/ansible/pull/83831)."
+  - "Fix ``SemanticVersion.parse()`` to store the version string so that ``__repr__`` reports it instead of ``None`` (https://github.com/ansible/ansible/pull/83831)."

changelogs/fragments/83874-include-parse-error-location.yml

@@ -0,0 +1,4 @@
+bugfixes:
+  - >-
+    include_tasks - Display location when attempting to load a task list where ``include_*`` did not specify any value -
+    https://github.com/ansible/ansible/issues/83874

changelogs/fragments/83960-dnf5-state-installed-fix.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - "dnf5 - re-introduce the ``state: installed`` alias to ``state: present`` (https://github.com/ansible/ansible/issues/83960)"

changelogs/fragments/PowerShell-AddType-temp.yml

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

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

changelogs/fragments/add_systemd_facts.yml

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

changelogs/fragments/ansible-config-validate.yml

@@ -0,0 +1,2 @@
+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

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

changelogs/fragments/ansible-doc-inicate.yml

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

changelogs/fragments/ansible-doc.yml

@@ -0,0 +1,3 @@
+---
+bugfixes:
+  - ansible-doc - handle no_fail condition for role.

changelogs/fragments/ansible-galaxy-install-archive-url-timeout.yml

@@ -0,0 +1,4 @@
+bugfixes:
+- >-
+  ``ansible-galaxy role install`` - update the default timeout to download
+  archive URLs from 20 seconds to 60 (https://github.com/ansible/ansible/issues/83521).

changelogs/fragments/ansible-galaxy-install-help.yml

@@ -0,0 +1,5 @@
+bugfixes:
+- >-
+  Add descriptions for ``ansible-galaxy install --help` and ``ansible-galaxy role|collection install --help``.
+- >-
+  ``ansible-galaxy install --help`` - Fix the usage text and document that the requirements file passed to ``-r`` can include collections and roles.

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

@@ -0,0 +1,2 @@
+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-coverage-update.yml

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

changelogs/fragments/ansible-test-error-message-improvement.yml

@@ -0,0 +1,2 @@
+minor_changes:
+  - ansible-test - Improve the error message shown when an unknown ``--remote`` or ``--docker`` option is given.

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

@@ -0,0 +1,2 @@
+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 5.0.0.

changelogs/fragments/ansible-test-no-egg-info.yml

@@ -0,0 +1,2 @@
+minor_changes:
+  - ansible-test - An ``ansible_core.egg-info`` directory is no longer generated when running tests.

changelogs/fragments/ansible-test-platform-updates.yml

@@ -0,0 +1,12 @@
+minor_changes:
+  - ansible-test - Replace Fedora 39 container and remote with Fedora 40.
+  - ansible-test - Replace Alpine 3.19 container and remote with Alpine 3.20.
+  - ansible-test - Replace Ubuntu 20.04 container with Ubuntu 24.04 container.
+  - ansible-test - Add Ubuntu 24.04 remote.
+  - ansible-test - Replace RHEL 9.3 remote with RHEL 9.4.
+  - ansible-test - Replace FreeBSD 14.0 remote with FreeBSD 14.1.
+known_issues:
+  - ansible-test - When using the Fedora 40 container with Podman on a Ubuntu 24.04 host,
+    the ``unix-chkpwd`` AppArmor profile must be disabled on the host to allow SSH connections to the container.
+  - ansible-test - When using ansible-test containers with Podman on a Ubuntu 24.04 host,
+    ansible-test must be run as a non-root user to avoid permission issues caused by AppArmor.

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

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

changelogs/fragments/ansible-test-sanity-empty-init.yml

@@ -0,0 +1,2 @@
+minor_changes:
+  - ansible-test - The ``empty-init`` sanity test no longer applies to ``module_utils`` packages.

changelogs/fragments/ansible-test-sanity-test-requirements.yml

@@ -0,0 +1,2 @@
+minor_changes:
+  - ansible-test - Updated the frozen requirements for all sanity tests.

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

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

changelogs/fragments/ansible-test-venv-bootstrap.yml

@@ -0,0 +1,3 @@
+minor_changes:
+  - ansible-test - Virtual environments created by ansible-test no longer include the ``wheel`` or ``setuptools`` packages.
+  - ansible-test - Upgrade ``pip`` used in ansible-test managed virtual environments from version 24.0 to 24.2.

changelogs/fragments/ansible-test-vyos.yml

@@ -0,0 +1,2 @@
+minor_changes:
+  - ansible-test - Removed the ``vyos/1.1.8`` network remote as it is no longer functional.

changelogs/fragments/ansible-test-windows-remote.yml

@@ -0,0 +1,2 @@
+minor_changes:
+  - ansible-test - Connection options can be set for ansible-test managed remote Windows instances.

changelogs/fragments/ansible_connection_path.yml

@@ -0,0 +1,8 @@
+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

@@ -0,0 +1,2 @@
+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

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

changelogs/fragments/apt_cache.yml

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

changelogs/fragments/assemble.yml

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

changelogs/fragments/atomic_update_perms_time.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - module_utils atomic_move (used by most file based modules), now correctly handles permission copy and setting mtime correctly across all paths

changelogs/fragments/become-runas-system.yml

@@ -0,0 +1,4 @@
+bugfixes:
+  - ->
+    runas become - Generate new token for the SYSTEM token to use for become. This should result in the full SYSTEM
+    token being used and problems starting the process that fails with ``The process creation has been blocked``.

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

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

changelogs/fragments/colors_for_included_events.yml

@@ -0,0 +1,4 @@
+bugfixes:
+  - COLOR_SKIP will not alter "included" events color display anymore.
+minor_changes:
+  - Introducing COLOR_INCLUDED parameter. This can set a specific color for "included" events.

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

@@ -0,0 +1,3 @@
+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/correct_connection_callback.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - Callbacks now correctly get the resolved connection plugin name as the connection used.

changelogs/fragments/darwin_facts.yml

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

changelogs/fragments/delay_type.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - delay keyword is now a float, matching the underlying 'time' API and user expectations.

changelogs/fragments/deprecate-safe-evals.yml

@@ -0,0 +1,2 @@
+deprecated_features:
+  - Deprecate ``ansible.module_utils.basic.AnsibleModule.safe_eval`` and ``ansible.module_utils.common.safe_eval`` as they are no longer used.

changelogs/fragments/dinit.yml

@@ -0,0 +1,3 @@
+---
+minor_changes:
+  - service_mgr - add support for dinit service manager (https://github.com/ansible/ansible/pull/83489).

changelogs/fragments/display_fix_log_severity.yml

@@ -0,0 +1,4 @@
+bugfixes:
+  - display now does a better job of mapping warnings/errors to the proper log severity when using ansible.log. We still use color as a fallback mapping (now prioritiezed by severity) but mostly rely on it beind directly set by warnning/errors calls.
+minor_changes:
+  - ansible.log now also shows log severity field

changelogs/fragments/dnf-exceptions-vs-text.yml

@@ -0,0 +1,2 @@
+minor_changes:
+  - dnf - minor internal changes in how the errors from the dnf API are handled; rely solely on the exceptions rather than inspecting text embedded in them

changelogs/fragments/dnf-remove-legacy-code.yml

@@ -0,0 +1,2 @@
+minor_changes:
+  - dnf - remove legacy code for unsupported dnf versions

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

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

changelogs/fragments/dnf_handle_downloaderror.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - dnf - Ensure that we are handling DownloadError properly in the dnf module

changelogs/fragments/dwim_is_role_fix_task_relative.yml

@@ -0,0 +1,2 @@
+bugfixes:
+  - Fix using the current task's directory for looking up relative paths within roles (https://github.com/ansible/ansible/issues/82695).

changelogs/fragments/empty_log_path.yml

@@ -0,0 +1,3 @@
+---
+bugfixes:
+  - display - warn user about empty log filepath (https://github.com/ansible/ansible/issues/79959).