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

CI:

• Replace Fedora 41 with Fedora 43 in the Testing Farm CI workflow matrix and supported platforms list, updating corresponding Ansible versions.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the Testing Farm GitHub Actions workflow to drop Fedora 41 from CI, add Fedora 43, and align the Ansible matrix versions accordingly.

Flow diagram for updated supported_platforms selection in tft.yml

flowchart TD
  A[Start workflow] --> B[Set meta_main to meta/main.yml]
  B --> C[Check if galaxy_tags contains fedora]
  C -->|Yes| D[Append Fedora-42 to supported_platforms]
  D --> E[Append Fedora-43 to supported_platforms]
  C -->|No| F[Skip generic Fedora platforms]

  E --> G[Check if galaxy_tags contains explicit fedoraN tag]
  F --> G

  G --> H[Process specific Fedora versions based on tags]
  H --> I[Build matrix.platforms from supported_platforms]
  I --> J[Run Testing Farm CI matrix jobs]
  J --> K[End workflow]

Loading

File-Level Changes

Change	Details	Files
Update supported Fedora versions in Testing Farm job setup logic.	Remove Fedora-41 from the dynamically constructed supported_platforms list. Ensure Fedora-42 remains in supported_platforms. Add Fedora-43 to the supported_platforms list used for Testing Farm runs.	.github/workflows/tft.yml
Adjust Testing Farm CI matrix to test on Fedora 43 with appropriate Ansible version and drop Fedora 41.	Remove the Fedora-41 / Ansible 2.17 matrix entry. Keep the Fedora-42 matrix entry but bump its Ansible version to 2.19 as defined. Add a new Fedora-43 matrix entry configured to use 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 reviewed your changes and they look great!

---

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.}