ci: Add Fedora 43, remove Fedora 41 from Testing Farm CI

[richm]

Add Fedora 43, remove Fedora 41 from Testing Farm CI

Signed-off-by: Rich Megginson rmeggins@redhat.com

Summary by Sourcery

Update Testing Farm GitHub workflow to test against the current Fedora releases.

CI:

• Replace Fedora 41 with Fedora 43 in the Testing Farm CI workflow matrix and supported platforms list.
• Align Ansible versions in the CI matrix with the updated Fedora platform coverage.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates Testing Farm CI workflow to drop Fedora 41 support and add Fedora 43 with appropriate Ansible versions, while keeping Fedora 42 in the test matrix and supported platforms detection.

File-Level Changes

Change	Details	Files
Update dynamic supported platforms list in Testing Farm workflow to track Fedora 42 and 43 instead of 41.	Remove Fedora 41 from the auto-populated supported_platforms string when Fedora is detected in galaxy tags. Ensure Fedora 42 remains in supported_platforms and append Fedora 43 as an additional supported Fedora release.	.github/workflows/tft.yml
Adjust Testing Farm job matrix to remove Fedora 41 and add Fedora 43 with a newer Ansible version.	Remove the Fedora-41 / Ansible 2.17 matrix entry from the Testing Farm CI job. Keep the Fedora-42 entry but bump coverage by adding a Fedora-43 matrix entry using Ansible 2.20.	.github/workflows/tft.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location> `.github/workflows/tft.yml:103-104` </location>
<code_context>
-            ansible_version: 2.17
           - platform: Fedora-42
             ansible_version: 2.19
+          - platform: Fedora-43
+            ansible_version: 2.20
           - platform: CentOS-7-latest
             ansible_version: 2.9
</code_context>

<issue_to_address>
**issue (bug_risk):** Quote the `ansible_version: 2.20` value to avoid YAML treating it as a numeric and normalizing it to `2.2`.

Because YAML treats `2.20` as a number, it may be read back as `2.2`, which can lead to installing the wrong Ansible version if this value is used in package specs (e.g., `ansible==${{ matrix.ansible_version }}`). Quoting it as a string (`"2.20"`) avoids this and preserves the intended version.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

issue (bug_risk): Quote the ansible_version: 2.20 value to avoid YAML treating it as a numeric and normalizing it to 2.2.

Because YAML treats 2.20 as a number, it may be read back as 2.2, which can lead to installing the wrong Ansible version if this value is used in package specs (e.g., ansible==${{ matrix.ansible_version }}). Quoting it as a string ("2.20") avoids this and preserves the intended version.