Bump devel version to 2.20.0.dev0 (#85409)

* Limit askpass prompts to single attempt

OpenSSH client option NumberOfPasswordPrompts defaults to 3 so in case
an incorrect connection password is provided it is excessively tried 3
times. Not only that but running the `_ssh_askpass` entry point multiple
times (via ssh) results in `json.decoder.JSONDecodeError` as after the
first run the shared memory is zero'd and the subsequent runs end up
calling `json.loads` on empty data.

`json.decoder.JSONDecodeError` does not happen prior to Python 3.13 as
the share memory is unlinked automatically on `.close()` and the
`_ssh_askpass` entry point exits with return code 1 before attempting to
load zero'd memory.

Fixes #85359

* changelog and tests

* Update changelogs/fragments/85359-askpass-incorrect-password-retries.yml

Co-authored-by: Matt Davis <6775756+nitzmahone@users.noreply.github.com>

* Update lib/ansible/cli/_ssh_askpass.py

Co-authored-by: Martin Krizek <martin.krizek@gmail.com>

* Avoid race condition in second unlink

---------

Co-authored-by: Matt Davis <6775756+nitzmahone@users.noreply.github.com>
Co-authored-by: Matt Clay <matt@mystile.com>

.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,12 +54,12 @@ stages:
           nameFormat: Python {0}
           testFormat: units/{0}
           targets:
-            - 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:
@@ -68,39 +68,54 @@ stages:
           nameFormat: Server {0}
           testFormat: windows/{0}/1
           targets:
-            - test: 2016
-            - test: 2019
-            - test: 2022
+            - name: 2016 WinRM HTTP
+              test: 2016/winrm/http
+            - 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 14.3
-              test: macos/14.3
-            - name: RHEL 9.3 py39
-              test: rhel/9.3@3.9
-            - name: RHEL 9.3 py311
-              test: rhel/9.3@3.11
-            - name: FreeBSD 13.3
-              test: freebsd/13.3
-            - name: FreeBSD 14.0
-              test: freebsd/14.0
+            - name: macOS 15.3
+              test: macos/15.3
+            - name: RHEL 9.5 py39
+              test: rhel/9.5@3.9
+            - name: RHEL 9.5 py312
+              test: rhel/9.5@3.12
+            - name: RHEL 10.0
+              test: rhel/10.0
+            - name: FreeBSD 13.5
+              test: freebsd/13.5
+            - name: FreeBSD 14.2
+              test: freebsd/14.2
           groups:
             - 1
             - 2
       - template: templates/matrix.yml  # context/controller
         parameters:
           targets:
-            - name: macOS 14.3
-              test: macos/14.3
-            - name: RHEL 9.3
-              test: rhel/9.3
-            - name: FreeBSD 13.3
-              test: freebsd/13.3
-            - name: FreeBSD 14.0
-              test: freebsd/14.0
+            - name: macOS 15.3
+              test: macos/15.3
+            - name: RHEL 9.5
+              test: rhel/9.5
+            - name: RHEL 10.0
+              test: rhel/10.0
+            - name: FreeBSD 13.5
+              test: freebsd/13.5
+            - name: FreeBSD 14.2
+              test: freebsd/14.2
           groups:
             - 3
             - 4
@@ -108,48 +123,58 @@ stages:
       - template: templates/matrix.yml  # context/controller (ansible-test container management)
         parameters:
           targets:
-            - name: Alpine 3.19
-              test: alpine/3.19
-            - name: Fedora 39
-              test: fedora/39
-            - name: RHEL 9.3
-              test: rhel/9.3
-            - name: Ubuntu 22.04
-              test: ubuntu/22.04
+            - name: Alpine 3.21
+              test: alpine/3.21
+            - name: Fedora 41
+              test: fedora/41
+            - name: RHEL 9.5
+              test: rhel/9.5
+            - name: RHEL 10.0
+              test: rhel/10.0
+            - name: Ubuntu 24.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
-              test: alpine319
-            - name: Fedora 39
-              test: fedora39
-            - name: Ubuntu 20.04
-              test: ubuntu2004
+            - name: Alpine 3.21
+              test: alpine321
+            - name: Fedora 41
+              test: fedora41
             - 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
-              test: alpine319
-            - name: Fedora 39
-              test: fedora39
-            - name: Ubuntu 22.04
-              test: ubuntu2204
+            - name: Alpine 3.21
+              test: alpine321
+            - name: Fedora 41
+              test: fedora41
+            - name: Ubuntu 24.04
+              test: ubuntu2404
           groups:
             - 3
             - 4
             - 5
+      - template: templates/matrix.yml  # context/target (dnf-oldest, dnf-latest)
+        parameters:
+          testFormat: linux/{0}
+          targets:
+            - name: Fedora 41
+              test: fedora41
+          groups:
+            - 7
   - stage: Galaxy
     dependsOn: []
     jobs:
@@ -158,9 +183,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:
@@ -169,9 +194,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: []
@@ -181,9 +206,20 @@ stages:
           nameFormat: Server {0}
           testFormat: i/windows/{0}
           targets:
-            - test: 2016
-            - test: 2019
-            - test: 2022
+            - name: 2016 WinRM HTTP
+              test: 2016/winrm/http
+            - 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:
@@ -193,8 +229,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."
-
-    platforms=(
-        --windows "${version}"
-    )
+    echo "Running Windows integration tests for the version ${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[@]}" \
-    --docker default --python "${python_default}" \
-    --remote-terminate always --remote-stage "${stage}" --remote-provider "${provider}"
+    --controller "docker:default,python=${python_default}" \
+    --target "remote:windows/${version},connection=${connection}+${connection_setting},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."
-
-    platforms=(
-        --windows "${version}"
-    )
+    echo "Running Windows integration tests for the version ${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}" \
-        --docker default --python "${version}" \
-        --remote-terminate "${terminate}" --remote-stage "${stage}" --remote-provider "${provider}"
+        --changed-all-target "${changed_all_target}" --changed-all-mode "${changed_all_mode}" \
+        --controller "docker:default,python=${py_version}" \
+        --target "remote:windows/${version},connection=${connection}+${connection_setting},provider=${provider}" \
+        --remote-terminate "${terminate}" --remote-stage "${stage}"
 done

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

@@ -9,11 +9,11 @@ from __future__ import annotations
 import argparse
 import dataclasses
 import pathlib
-import shutil
+import shlex
 import subprocess
 import tempfile
 import typing as t
-import urllib.request
+import venv
 
 
 @dataclasses.dataclass(frozen=True)
@@ -43,6 +43,27 @@ def parse_args() -> Args:
     return Args(**kwargs)
 
 
+def run(*args: str | pathlib.Path) -> None:
+    cmd = [str(arg) for arg in args]
+    print(f'==> {shlex.join(cmd)}', flush=True)
+    subprocess.run(cmd, check=True)
+
+
+def install_codecov(dest: pathlib.Path) -> pathlib.Path:
+    package = 'codecov-cli'
+    version = '11.0.3'
+
+    venv_dir = dest / 'venv'
+    python_bin = venv_dir / 'bin' / 'python'
+    codecov_bin = venv_dir / 'bin' / 'codecovcli'
+
+    venv.create(venv_dir, with_pip=True)
+
+    run(python_bin, '-m', 'pip', 'install', f'{package}=={version}', '--disable-pip-version-check')
+
+    return codecov_bin
+
+
 def process_files(directory: pathlib.Path) -> t.Tuple[CoverageFile, ...]:
     processed = []
     for file in directory.joinpath('reports').glob('coverage*.xml'):
@@ -57,45 +78,43 @@ def process_files(directory: pathlib.Path) -> t.Tuple[CoverageFile, ...]:
     return tuple(processed)
 
 
-def upload_files(codecov_bin: pathlib.Path, files: t.Tuple[CoverageFile, ...], dry_run: bool = False) -> None:
+def upload_files(codecov_bin: pathlib.Path, config_file: pathlib.Path, files: t.Tuple[CoverageFile, ...], dry_run: bool = False) -> None:
     for file in files:
         cmd = [
-            str(codecov_bin),
-            '--name', file.name,
-            '--file', str(file.path),
+            codecov_bin,
+            '--disable-telem',
+            '--codecov-yml-path',
+            config_file,
+            'upload-process',
+            '--disable-search',
+            '--disable-file-fixes',
+            '--plugin',
+            'noop',
+            '--name',
+            file.name,
+            '--file',
+            file.path,
         ]
+
         for flag in file.flags:
-            cmd.extend(['--flags', flag])
+            cmd.extend(['--flag', flag])
 
         if dry_run:
-            print(f'DRY-RUN: Would run command: {cmd}')
-            continue
+            cmd.append('--dry-run')
 
-        subprocess.run(cmd, check=True)
+        run(*cmd)
 
 
-def download_file(url: str, dest: pathlib.Path, flags: int, dry_run: bool = False) -> None:
-    if dry_run:
-        print(f'DRY-RUN: Would download {url} to {dest} and set mode to {flags:o}')
-        return
-
-    with urllib.request.urlopen(url) as resp:
-        with dest.open('w+b') as f:
-            # Read data in chunks rather than all at once
-            shutil.copyfileobj(resp, f, 64 * 1024)
-
-    dest.chmod(flags)
-
-
-def main():
+def main() -> None:
     args = parse_args()
-    url = 'https://ci-files.testing.ansible.com/codecov/linux/codecov'
-    with tempfile.TemporaryDirectory(prefix='codecov-') as tmpdir:
-        codecov_bin = pathlib.Path(tmpdir) / 'codecov'
-        download_file(url, codecov_bin, 0o755, args.dry_run)
 
+    with tempfile.TemporaryDirectory(prefix='codecov-') as tmpdir:
+        config_file = pathlib.Path(tmpdir) / 'config.yml'
+        config_file.write_text('')
+
+        codecov_bin = install_codecov(pathlib.Path(tmpdir))
         files = process_files(args.path)
-        upload_files(codecov_bin, files, args.dry_run)
+        upload_files(codecov_bin, config_file, files, args.dry_run)
 
 
 if __name__ == '__main__':

.azure-pipelines/scripts/report-coverage.sh

@@ -12,6 +12,6 @@ if ! ansible-test --help >/dev/null 2>&1; then
     pip install https://github.com/ansible/ansible/archive/devel.tar.gz --disable-pip-version-check
 fi
 
-# Generate stubs using docker (if supported) otherwise fall back to using a virtual environment instead.
-# The use of docker is required when Powershell code is present, but Ansible 2.12 was the first version to support --docker with coverage.
-ansible-test coverage xml --group-by command --stub --docker --color -v || ansible-test coverage xml --group-by command --stub --venv --color -v
+# Generate stubs using docker.
+# The use of docker is mandatory when Powershell code is present.
+ansible-test coverage xml --group-by command --stub --docker --color -v

.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,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
-      [starting a mailing list thread or chatting in IRC][ML||IRC].
+      **Tip:** If you are seeking community support, please see
+      [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--bug_report.yml#mailing-list-information
+      [communication]:
+      https://docs.ansible.com/ansible/devel/community/communication.html
 
       [issue search]: ../search?q=is%3Aissue&type=issues
 
@@ -46,23 +47,7 @@ body:
 - type: dropdown
   attributes:
     label: Issue Type
-    description: >
-      Please select the single available option in the drop-down.
-
-      <details>
-        <summary>
-          <em>Why?</em>
-        </summary>
-
-        We would do it by ourselves but unfortunatelly, the curent
-        edition of GitHub Issue Forms Alpha does not support this yet 🤷
-
-
-        _We will make it easier in the future, once GitHub
-        supports dropdown defaults. Promise!_
-
-      </details>
-    # FIXME: Once GitHub allows defining the default choice, update this
+    description: This is a marker for our automatic bot. Do not change it.
     options:
     - Bug Report
   validations:
@@ -151,7 +136,7 @@ body:
   attributes:
     label: Steps to Reproduce
     description: |
-      Describe exactly how to reproduce the problem, using a minimal test-case. It would *really* help us understand your problem if you could also pased any playbooks, configs and commands you used.
+      Describe exactly how to reproduce the problem, using a minimal test-case. It would *really* help us understand your problem if you could also provide any playbooks, configs and commands you used.
 
       **HINT:** You can paste https://gist.github.com links for larger files.
     value: |
@@ -258,7 +243,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,15 +11,15 @@ 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
-  url: https://docs.ansible.com/ansible/latest/community/communication.html?utm_medium=github&utm_source=issue_template_chooser#mailing-list-information
+- name: 💬 Talk to the community
+  url: https://docs.ansible.com/ansible/devel/community/communication.html?utm_medium=github&utm_source=issue_template_chooser#forum
   about: Please ask and answer usage questions here
 - name: ⚡ Working groups
-  url: https://github.com/ansible/community/wiki
+  url: https://forum.ansible.com/g?utm_medium=github&utm_source=issue_template_chooser
   about: Interested in improving a specific area? Become a part of a working group!
 - name: 💼 For Enterprise
   url: https://www.ansible.com/products/engine?utm_medium=github&utm_source=issue_template_chooser

.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
-      [starting a mailing list thread or chatting in IRC][ML||IRC].
+      **Tip:** If you are seeking community support, please see
+      [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
 
@@ -82,20 +84,7 @@ body:
 - type: dropdown
   attributes:
     label: Issue Type
-    description: >
-      Please select the single available option in the drop-down.
-
-      <details>
-        <summary>
-          <em>Why?</em>
-        </summary>
-
-
-        _We will make it easier in the future, once GitHub
-        supports dropdown defaults. Promise!_
-
-      </details>
-    # FIXME: Once GitHub allows defining the default choice, update this
+    description: This is a marker for our automatic bot. Do not change it.
     options:
     - Documentation Report
   validations:
@@ -205,7 +194,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
-      for this.
+      start a discussion in the [Ansible forum][forum].
 
 
       <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
-      [starting a mailing list thread or chatting in IRC][ML||IRC].
+      **Tip:** If you are seeking community support, please see
+      [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]:
-        https://docs.ansible.com/ansible-core/devel/community/communication.html?utm_medium=github&utm_source=issue_form--feature_request.yml#irc-meetings
+      [communication]:
+      https://docs.ansible.com/ansible/devel/community/communication.html
 
       [issue search]: ../search?q=is%3Aissue&type=issues
 
-      [ML||IRC]:
-      https://docs.ansible.com/ansible-core/devel/community/communication.html?utm_medium=github&utm_source=issue_form--feature_request.yml#mailing-list-information
+      [forum help]:
+      https://forum.ansible.com/c/help/6
 
       [new proposal]: ../../proposals/issues/new
 
@@ -101,23 +101,7 @@ body:
 - type: dropdown
   attributes:
     label: Issue Type
-    description: >
-      Please select the single available option in the drop-down.
-
-      <details>
-        <summary>
-          <em>Why?</em>
-        </summary>
-
-        We would do it by ourselves but unfortunatelly, the curent
-        edition of GitHub Issue Forms Alpha does not support this yet 🤷
-
-
-        _We will make it easier in the future, once GitHub
-        supports dropdown defaults. Promise!_
-
-      </details>
-    # FIXME: Once GitHub allows defining the default choice, update this
+    description: This is a marker for our automatic bot. Do not change it.
     options:
     - Feature Idea
   validations:
@@ -185,7 +169,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/ISSUE_TEMPLATE/internal_issue.md

@@ -0,0 +1,10 @@
+---
+name: Internal Issue
+about: Free-form issue creation for core maintainer use only.
+title: ''
+labels: [core-internal]
+assignees: ''
+---
+
+
+@ansibot bot_skip

.github/ISSUE_TEMPLATE/pre_release.yml

@@ -0,0 +1,42 @@
+name: Pre-Release Bug Report
+description: File a bug report against a pre-release version
+labels:
+  - bug
+  - pre_release
+assignees:
+  - nitzmahone
+  - mattclay
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## Bug Report
+  - type: textarea
+    attributes:
+      label: Ansible Version
+      description: Paste the full output from `ansible --version` below.
+      render: console
+      placeholder: $ ansible --version
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Summary
+      description: Describe the issue with any relevant steps to reproduce.
+    validations:
+      required: true
+  - type: dropdown
+    attributes:
+      label: <!-- Bot instructions (ignore this) -->
+      options:
+        - |
+          <!--
+          ### Component Name
+          bin/ansible
+          ### Issue Type
+          Bug Report
+          ### Configuration
+          ### OS / Environment
+          -->
+    validations:
+      required: true

.github/PULL_REQUEST_TEMPLATE/Bug fix.md

@@ -2,19 +2,8 @@
 
 <!--- Describe the change below, including rationale and design decisions -->
 
-<!--- HINT: Include "Fixes #nnn" if you are fixing an existing issue -->
+<!--- Add "Fixes #1234" or steps to reproduce the problem if there is no corresponding 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

@@ -2,18 +2,8 @@
 
 <!--- Describe the change below, including rationale -->
 
-<!--- HINT: Include "Closes #nnn" if you are fixing an existing issue -->
+<!--- Add "Fixes #1234" if there is a corresponding 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

@@ -2,18 +2,8 @@
 
 <!--- Describe the change below, including rationale and design decisions -->
 
-<!--- HINT: Include "Resolves #nnn" if you are fixing an existing issue -->
+<!--- Add "Fixes #1234" if there is a corresponding 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/Tests.md

@@ -2,19 +2,8 @@
 
 <!--- Describe the change below, including rationale and design decisions -->
 
-<!--- HINT: Include "Closes #nnn" if you are fixing an existing issue -->
+<!--- Add "Fixes #1234" if there is a corresponding 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

@@ -2,7 +2,7 @@
 
 <!--- Describe the change below, including rationale and design decisions -->
 
-<!--- HINT: Include "Fixes #nnn" if you are fixing an existing issue -->
+<!--- Add "Fixes #1234" or steps to reproduce the problem if there is no corresponding issue -->
 
 ##### ISSUE TYPE
 
@@ -12,14 +12,3 @@
 - 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.20.0  TBD
+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

.gitignore

@@ -92,9 +92,14 @@ 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
+# PowerShell signed hashlist
+lib/ansible/config/powershell_signatures.psd1
+*.authenticode
 # test stuff
 /test/integration/cloud-config-*.*
 !/test/integration/cloud-config-*.*.template

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 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 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/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
-  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.
+  including how to submit bug reports and code to Ansible.
 * 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/changelog.yaml

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

changelogs/fragments/49809_apt_repository.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-- apt_repository - do not modify repo files if the file is a symlink (https://github.com/ansible/ansible/issues/49809).

changelogs/fragments/76727-chattr-fix-for-backups-of-symlinks.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - check if there are attributes to set before attempting to set them (https://github.com/ansible/ansible/issues/76727)

changelogs/fragments/77077_iptables.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-- iptables - set jump to DSCP when set_dscp_mark or set_dscp_mark_class is set (https://github.com/ansible/ansible/issues/77077).

changelogs/fragments/77336-include_role-callbacks-stats.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - "``include_role`` - properly execute ``v2_playbook_on_include`` and ``v2_runner_on_failed`` callbacks as well as increase ``ok`` and ``failed`` stats in the play recap, when appropriate (https://github.com/ansible/ansible/issues/77336)"

changelogs/fragments/78703_undefined.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-  - Do not print undefined error message twice (https://github.com/ansible/ansible/issues/78703).

changelogs/fragments/79705-fix-ensure-path-to-collection-argument-doesnt-have-backslash.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - ansible-galaxy - ensure path to ansible collection when installing or downloading doesn't have a backslash (https://github.com/ansible/ansible/pull/79705).

changelogs/fragments/79945-host_group_vars-improvements.yml

@@ -1,5 +0,0 @@
-bugfixes:
-  - Cache host_group_vars after instantiating it once and limit the amount of repetitive work it needs to do every time it runs.
-  - Call PluginLoader.all() once for vars plugins, and load vars plugins that run automatically or are enabled specifically by name subsequently.
-deprecated_features:
-  - Old style vars plugins which use the entrypoints `get_host_vars` or `get_group_vars` are deprecated. The plugin should be updated to inherit from `BaseVarsPlugin` and define a `get_vars` method as the entrypoint.

changelogs/fragments/80110-repos-gpgcheck.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - dnf - properly set gpg check options on enabled repositories according to the ``disable_gpg_check`` option (https://github.com/ansible/ansible/issues/80110)

changelogs/fragments/80267-ansible_builtin_user-remove-user-not-found-warning.yml

@@ -1,2 +0,0 @@
-minor_changes:
-  - ansible.builtin.user - Remove user not found warning (https://github.com/ansible/ansible/issues/80267)

changelogs/fragments/80478-extend-mount-info.yml

@@ -1,2 +0,0 @@
-minor_changes:
-  - "Add ``dump`` and ``passno`` mount information to facts component (https://github.com/ansible/ansible/issues/80478)"

changelogs/fragments/80561.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-- Provide additional information about the alternative plugin in the deprecation message (https://github.com/ansible/ansible/issues/80561).

changelogs/fragments/80590-dnf-skip_broken-unavailable-pkgs.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - dnf - properly skip unavailable packages when ``skip_broken`` is enabled (https://github.com/ansible/ansible/issues/80590)

changelogs/fragments/80882-Amazon-os-family-compat.yaml

@@ -1,2 +0,0 @@
-bugfixes:
-- Interpreter discovery - Add ``Amzn`` to ``OS_FAMILY_MAP`` for correct family fallback for interpreter discovery (https://github.com/ansible/ansible/issues/80882).

changelogs/fragments/80975-systemd-detect.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-  - Consolidate systemd detection logic into one place (https://github.com/ansible/ansible/issues/80975).

changelogs/fragments/80995-include-all-var-files.yml

@@ -1,2 +0,0 @@
-bugfixes:
-- include_vars - fix calculating ``depth`` relative to the root and ensure all files are included (https://github.com/ansible/ansible/issues/80987).

changelogs/fragments/81053-templated-tags-inheritance.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - Properly template tags in parent blocks (https://github.com/ansible/ansible/issues/81053)

changelogs/fragments/81188_better_error.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-  - Reword the error message when the module fails to parse parameters in JSON format (https://github.com/ansible/ansible/issues/81188).

changelogs/fragments/81532-fix-nested-flush_handlers.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - flush_handlers - properly handle a handler failure in a nested block when ``force_handlers`` is set (http://github.com/ansible/ansible/issues/81532)

changelogs/fragments/81584-daemonize-follow-up-fixes.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - "``ansible.module_utils.service`` - ensure binary data transmission in ``daemonize()``"

changelogs/fragments/81606-ansible-galaxy-collection-pre-releases.yml

@@ -1,16 +0,0 @@
----
-
-bugfixes:
-- >-
-  ansible-galaxy - started allowing the use of pre-releases
-  for dependencies on any level of the dependency tree that
-  specifically demand exact pre-release versions of
-  collections and not version ranges.
-  (https://github.com/ansible/ansible/pull/81606)
-- >-
-  ansible-galaxy - started allowing the use of pre-releases
-  for collections that do not have any stable versions
-  published.
-  (https://github.com/ansible/ansible/pull/81606)
-
-...

changelogs/fragments/81628_galaxy_verify.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-- galaxy - skip verification for unwanted Python compiled bytecode files (https://github.com/ansible/ansible/issues/81628).

changelogs/fragments/81638-blockinfile.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - "blockinfile - when ``create=true`` is used with a filename without path, the module crashed (https://github.com/ansible/ansible/pull/81638)."

changelogs/fragments/81659_varswithsources.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-- vars - handle exception while combining VarsWithSources and dict (https://github.com/ansible/ansible/issues/81659).

changelogs/fragments/81666-handlers-run_once.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - Fix ``run_once`` being incorrectly interpreted on handlers (https://github.com/ansible/ansible/issues/81666)

changelogs/fragments/81699-zip-permission.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - unarchive - add support for 8 character permission strings for zip archives (https://github.com/ansible/ansible/pull/81705).

changelogs/fragments/81713-distro.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-  - distro - bump bundled distro version from 1.6.0 to 1.8.0 (https://github.com/ansible/ansible/issues/81713).

changelogs/fragments/81714-remove-deprecated-jinja2_native_warning.yml

@@ -1,2 +0,0 @@
-removed_features:
-  - Remove deprecated JINJA2_NATIVE_WARNING environment variable (https://github.com/ansible/ansible/issues/81714)

changelogs/fragments/81716-ansible-doc.yml

@@ -1,3 +0,0 @@
----
-removed_features:
-  - Remove deprecated APIs from ansible-docs (https://github.com/ansible/ansible/issues/81716).

changelogs/fragments/81717-remove-deprecated-crypt-support.yml

@@ -1,2 +0,0 @@
-removed_features:
-  - Remove deprecated crypt support from ansible.utils.encrypt (https://github.com/ansible/ansible/issues/81717)

changelogs/fragments/81722-handler-subdir-include_tasks.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - Allow for searching handler subdir for included task via include_role (https://github.com/ansible/ansible/issues/81722)

changelogs/fragments/81732-cloudstack-test-container-1.7.0.yml

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

changelogs/fragments/81775-add-regex_replace-parameters.yml

@@ -1,3 +0,0 @@
----
-minor_changes:
-  - filter plugin - Add the count and mandatory_count parameters in the regex_replace filter

changelogs/fragments/81901-galaxy-requirements-format.yml

@@ -1,2 +0,0 @@
-bugfixes:
-- ansible-galaxy - Provide a better error message when using a requirements file with an invalid format - https://github.com/ansible/ansible/issues/81901

changelogs/fragments/81931-locale-related-parsing-error-git.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-  - Fix setting proper locale for git executable when running on non english systems, ensuring git output can always be parsed.

changelogs/fragments/81954-dnf-keepcache.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - "dnf - fix an issue when cached RPMs were left in the cache directory even when the keepcache setting was unset (https://github.com/ansible/ansible/issues/81954)"

changelogs/fragments/81978-launchpad-api-endpoint.yml

@@ -1,3 +0,0 @@
----
-minor_changes:
-  - apt_repository.py - use api.launchpad.net endpoint instead of launchpad.net/api

changelogs/fragments/81995-enable_file_cache.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - Enable file cache for vaulted files during vars lookup to fix a strong performance penalty in huge and complex playbboks. 

changelogs/fragments/82027_find.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
-    - find - do not fail on Permission errors (https://github.com/ansible/ansible/issues/82027).

changelogs/fragments/82066.yml

@@ -1,3 +0,0 @@
----
-minor_changes:
-  - removed the unused argument ``create_new_password`` from ``CLI.build_vault_ids`` (https://github.com/ansible/ansible/pull/82066).

changelogs/fragments/82175-fix-ansible-galaxy-role-import-rc.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - ansible-galaxy role import - exit with 1 when the import fails (https://github.com/ansible/ansible/issues/82175).

changelogs/fragments/82187-uri-handle-force.yml

@@ -1,6 +0,0 @@
----
-bugfixes:
-  - ansible.builtin.uri - the module was ignoring the ``force`` parameter and always
-    requesting a cached copy (via the ``If-Modified-Since`` header) when downloading
-    to an existing local file. Disable caching when ``force`` is ``true``, as
-    documented (https://github.com/ansible/ansible/issues/82166).

changelogs/fragments/82241-handler-include-tasks-from.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - Fix issue where an ``include_tasks`` handler in a role was not able to locate a file in ``tasks/`` when ``tasks_from`` was used as a role entry point and ``main.yml`` was not present (https://github.com/ansible/ansible/issues/82241)

changelogs/fragments/82353-ansible-sanity-examples.yml

@@ -1,4 +0,0 @@
----
-minor_changes:
-  - ansible-test - sanity test allows ``EXAMPLES`` to be multi-document YAML (https://github.com/ansible/ansible/issues/82353).
-  - ansible-test - document block name now included in error message for YAML parsing errors (https://github.com/ansible/ansible/issues/82353).

changelogs/fragments/82359_assemble_diff.yml

@@ -1,3 +0,0 @@
----
-bugfixes:
- - assemble - fixed missing parameter 'content' in _get_diff_data API (https://github.com/ansible/ansible/issues/82359).

changelogs/fragments/82363-multiple-handlers-with-recursive-notification.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - Run all handlers with the same ``listen`` topic, even when notified from another handler (https://github.com/ansible/ansible/issues/82363).

changelogs/fragments/82377-git-gpg-whitelist-allowlist.yml

@@ -1,3 +0,0 @@
----
-minor_changes:
-  - git module - gpg_allowlist name was added in 2.17 and we will eventually deprecate the gpg_whitelist alias.

changelogs/fragments/82387-unquote-strings-from-ini-files.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - Fix condition for unquoting configuration strings from ini files (https://github.com/ansible/ansible/issues/82387).

changelogs/fragments/82455-new-vmware-productname.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - "facts - detect VMware ESXi 8.0 virtualization by product name VMware20,1"

changelogs/fragments/82461-dnf-provides.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - dnf - fix an issue when installing a package by specifying a file it provides could result in installing a different package providing the same file than the package already installed resulting in resolution failure (https://github.com/ansible/ansible/issues/82461)

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

@@ -1,2 +0,0 @@
-minor_changes:
-  - "ansible-doc - treat double newlines in documentation strings as paragraph breaks. This is useful to create multi-paragraph notes in module/plugin documentation (https://github.com/ansible/ansible/pull/82465)."

changelogs/fragments/82496-add-alp-dolomite-suse-family.yaml

@@ -1,2 +0,0 @@
-bugfixes:
-  - distribution.py - Recognize ALP-Dolomite as part of the SUSE OS family in Ansible, fixing its previous misidentification (https://github.com/ansible/ansible/pull/82496).

changelogs/fragments/82574-ansible-test-ansible-doc-underscore.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - "ansible-test ansible-doc sanity test - do not remove underscores from plugin names in collections before calling ``ansible-doc`` (https://github.com/ansible/ansible/pull/82574)."

changelogs/fragments/82575-ansible-test-validate-modules-underscore.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - "ansible-test validate-modules sanity test - do not treat leading underscores for plugin names in collections as an attempted deprecation (https://github.com/ansible/ansible/pull/82575)."

changelogs/fragments/82580_constructed.yml

@@ -1,2 +0,0 @@
-minor_changes:
-  - "constructed inventory plugin - Adding a note that only group_vars of explicit groups are loaded (https://github.com/ansible/ansible/pull/82580)."

changelogs/fragments/82606-template-python-syntax-error.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - templating - ensure syntax errors originating from a template being compiled into Python code object result in a failure (https://github.com/ansible/ansible/issues/82606)

changelogs/fragments/82611_fix_alignment_apt_clean_with_ansible_apt_clean.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - ansible.builtin.apt - calling clean = true does not properly clean certain cache files such as /var/cache/apt/pkgcache.bin and /var/cache/apt/pkgcache.bin (https://github.com/ansible/ansible/issues/82611)

changelogs/fragments/82616-dnf-best-nobest.yml

@@ -1,6 +0,0 @@
-minor_changes:
-  - dnf - add the ``best`` option
-  - dnf5 - add the ``best`` option
-bugfixes:
-  - dnf - the ``nobest`` option only overrides the distribution default when explicitly used, and is used for all supported operations (https://github.com/ansible/ansible/issues/82616)
-  - dnf5 - the ``nobest`` option only overrides the distribution default when used

changelogs/fragments/82655-fix-ansible-loop-index-var-in-includedtasks.yml

@@ -1,2 +0,0 @@
-bugfixes:
-    - include_tasks - include `ansible_loop_var` and `ansible_index_var` in a loop (https://github.com/ansible/ansible/issues/82655).

changelogs/fragments/82675-fix-unsafe-templating-leading-to-type-error.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - template - Fix error when templating an unsafe string which corresponds to an invalid type in Python (https://github.com/ansible/ansible/issues/82600).

changelogs/fragments/82678-role-entrypoint-attributes.yml

@@ -1,2 +0,0 @@
-deprecated_features:
-  - "ansible-doc - role entrypoint attributes are deprecated and eventually will no longer be shown in ansible-doc from ansible-core 2.20 on (https://github.com/ansible/ansible/issues/82639, https://github.com/ansible/ansible/pull/82678)."

changelogs/fragments/82683-ansible-fact_cache-permissions-changed-after-ansible-coreupdate.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - Fixes permission for cache json file from 600 to 644 (https://github.com/ansible/ansible/issues/82683).

changelogs/fragments/82954-fix-older-connection-plugins.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - Fix check for missing _sub_plugin attribute in older connection plugins (https://github.com/ansible/ansible/pull/82954)

changelogs/fragments/a-g-install-version-None.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - ansible-galaxy role install - fix installing roles from Galaxy that have version ``None`` (https://github.com/ansible/ansible/issues/81832).

changelogs/fragments/ansible-galaxy-init-extra-vars.yml

@@ -1,5 +0,0 @@
-minor_changes:
-- >-
-  ``ansible-galaxy role|collection init`` - accept ``--extra-vars`` to
-  supplement/override the variables ``ansible-galaxy`` injects for templating
-  ``.j2`` files in the skeleton.

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

@@ -1,2 +0,0 @@
-bugfixes:
-  - ansible-galaxy role install - normalize tarfile paths and symlinks using ``ansible.utils.path.unfrackpath`` and consider them valid as long as the realpath is in the tarfile's role directory (https://github.com/ansible/ansible/issues/81965).

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

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

changelogs/fragments/ansible-test-added-macos-14.3.yml

@@ -1,6 +0,0 @@
----
-
-minor_changes:
-- ansible-test - Added a macOS 14.3 remote VM.
-
-...

changelogs/fragments/ansible-test-alpine-libexpat.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - ansible-test - The ``libexpat`` package is automatically upgraded during remote bootstrapping to maintain compatibility with newer Python packages.

changelogs/fragments/ansible-test-cgroup-split.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - ansible-test - Fix parsing of cgroup entries which contain a ``:`` in the path (https://github.com/ansible/ansible/issues/81977).

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

@@ -1,3 +0,0 @@
-minor_changes:
-- ansible-test - When invoking ``sleep`` in containers during container setup, the ``env`` command is used to avoid invoking
-                 the shell builtin, if present.

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

@@ -1,6 +0,0 @@
----
-
-bugfixes:
-- ansible-test — Python 3.8–3.12 will use ``coverage`` v7.3.2.
-
-...

changelogs/fragments/ansible-test-cryptography.yml

@@ -1,2 +0,0 @@
-minor_changes:
-  - ansible-test - Special handling for installation of ``cryptography`` has been removed, as it is no longer necessary.

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

@@ -1,3 +0,0 @@
-minor_changes:
-  - ansible-test - Update the base and default containers to use Ubuntu 22.04 for the base image.
-                   This also updates PowerShell to version 7.4.0 with .NET 8.0.0 and ShellCheck to version 0.8.0.

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

@@ -1,4 +0,0 @@
-minor_changes:
-- ansible-test - Updated the distro test containers to version 6.3.0 to include coverage 7.3.2 for Python 3.8+.
-                 The alpine3 container is now based on 3.18 instead of 3.17 and includes Python 3.11 instead of Python 3.10.
-- ansible-test - Updated the distro test containers to version 7.1.0.

changelogs/fragments/ansible-test-docker-forwards.yml

@@ -1,5 +0,0 @@
-bugfixes:
-- ansible-test - Properly detect docker host when using ``ssh://`` protocol for connecting to the docker daemon.
-- ansible-test - Explicitly supply ``ControlPath=none`` when setting up port forwarding over SSH to address
-  the scenario where the local ssh configuration uses ``ControlPath`` for all hosts, and would prevent
-  ports to be forwarded after the initial connection to the host.